Bug 6027 – bigint to!string conversion and its implications

I know about issue http://d.puremagic.com/issues/show_bug.cgi?id=5231 , but still the problem exists. It is ok (for me, at least) not to have an ability to use writeln(BigInt(16)). But the design decision not to have string toString() method also affects another parts of the library. There are at least two such places. First is to!string function. I think that it should work uniformly for all sensible datatypes, and I expect the following equation to work: to!string(123) == to!string(BigInt(123)), because I see no reason against it. Second is, maybe, an implication of the first. See issue http://d.puremagic.com/issues/show_bug.cgi?id=6023 . I think this is not a correct situation. There may be reasons why I can't use BigInt-valued random number, but these reasons certainly must not include the inability to do BigInt->string conversion without useless format specifiers.

See also issue 5970 and issue 5971

(In reply to comment #0) > I know about issue http://d.puremagic.com/issues/show_bug.cgi?id=5231 , but > still the problem exists. It is ok (for me, at least) not to have an ability to > use writeln(BigInt(16)). That worked in a previous release. It should still work.

Now to!string(BigInt(123)) works as expected. And bug 6023 is not relevant to toString issue. If there is other issues still, please reopen.