[Issue 5231] BigInt lacks a normal toString()

2015-06-09 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=5231 Andrei Alexandrescu changed: What|Removed |Added Version|unspecified |D2 --

[Issue 5231] BigInt lacks a normal toString()

2010-11-19 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5231 --- Comment #17 from bearophile_h...@eml.cc 2010-11-19 07:14:29 PST --- (In reply to comment #16) > This is a bug in format. Even the partial fix I made for bug 5237, makes > BigInt > print correctly, without any change to the BigInt code. > >

[Issue 5231] BigInt lacks a normal toString()

2010-11-19 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5231 Don changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Issue 5231] BigInt lacks a normal toString()

2010-11-18 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5231 --- Comment #15 from Jonathan M Davis 2010-11-18 14:32:17 PST --- Well, then I think that we agree on the desired eventual functionality. But I do think that in the interim, it would be a good idea to add string toString() to BigInt with the i

[Issue 5231] BigInt lacks a normal toString()

2010-11-18 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5231 --- Comment #14 from Don 2010-11-18 13:39:08 PST --- (In reply to comment #12) > So, you don't want writeln(bi); or to!string(bi) to work? No, that's not what I meant. > I would think that > ideally, BigInt would work exactly the same way tha

[Issue 5231] BigInt lacks a normal toString()

2010-11-18 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5231 --- Comment #13 from Jonathan M Davis 2010-11-18 12:33:01 PST --- Whoops. I meant %x, not %f for hex. Sorry about that. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because

[Issue 5231] BigInt lacks a normal toString()

2010-11-18 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5231 --- Comment #12 from Jonathan M Davis 2010-11-18 12:31:36 PST --- So, you don't want writeln(bi); or to!string(bi) to work? I would think that ideally, BigInt would work exactly the same way that integers do. to!string(i) -> decimal writeln(i

[Issue 5231] BigInt lacks a normal toString()

2010-11-18 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5231 --- Comment #11 from Don 2010-11-18 12:01:39 PST --- (In reply to comment #10) > (In reply to comment #9) > > > > If it was just a question of inefficiency, I would have implemented it. The > > issue is that it doesn't get the formatting strin

[Issue 5231] BigInt lacks a normal toString()

2010-11-18 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5231 --- Comment #10 from Steven Schveighoffer 2010-11-18 10:20:08 PST --- (In reply to comment #9) > > If it was just a question of inefficiency, I would have implemented it. The > issue is that it doesn't get the formatting string. > So > BigInt

[Issue 5231] BigInt lacks a normal toString()

2010-11-18 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5231 --- Comment #9 from Don 2010-11-18 08:42:45 PST --- (In reply to comment #8) > Second, it's they way things currently work. It's like saying you refuse to > have const functions because they should be inout, but inout doesn't work. > When to

[Issue 5231] BigInt lacks a normal toString()

2010-11-18 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5231 --- Comment #8 from Steven Schveighoffer 2010-11-18 06:30:23 PST --- Pardon me for saying so, but that's too short-sighted. first, it's not just a writeln/format change, it's a compiler change too. The compiler is the one who decides whether

[Issue 5231] BigInt lacks a normal toString()

2010-11-18 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5231 --- Comment #7 from Don 2010-11-18 05:58:20 PST --- (In reply to comment #6) > (In reply to comment #2) > So BigInt's aren't printable via writeln in protest? Yes. I refuse to play any part in propagating the toString() abomination. BigInt wi

[Issue 5231] BigInt lacks a normal toString()

2010-11-18 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5231 Steven Schveighoffer changed: What|Removed |Added CC||schvei...@yahoo.com --- Comment

[Issue 5231] BigInt lacks a normal toString()

2010-11-18 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5231 --- Comment #5 from nfx...@gmail.com 2010-11-18 00:57:38 PST --- (In reply to comment #4) > What is worrying is that void toString is nowhere documented. Does std.format > use it or what? Should be: is it supposed to use it? Of course it doesn'

[Issue 5231] BigInt lacks a normal toString()

2010-11-18 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5231 nfx...@gmail.com changed: What|Removed |Added CC||nfx...@gmail.com --- Comment #4 from

[Issue 5231] BigInt lacks a normal toString()

2010-11-18 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5231 --- Comment #3 from Jonathan M Davis 2010-11-18 00:24:35 PST --- void toString()? Normally, it's string toString(). The only problem that I'm aware of with regards to toString() design at the moment is the fact that it must be _exactly_ string

[Issue 5231] BigInt lacks a normal toString()

2010-11-18 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5231 Don changed: What|Removed |Added CC||clugd...@yahoo.com.au --- Comment #2 from Don 2

[Issue 5231] BigInt lacks a normal toString()

2010-11-17 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5231 bearophile_h...@eml.cc changed: What|Removed |Added CC||bearophile_h...@eml.cc --- Com