--- Comment #2 from Vladimir Matveev <> 2011-06-10 
23:48:18 PDT ---
(In reply to comment #1)
> The error message is the one returned when!string(BigInt) is
> called.
> std.bigint doesn't support!string. (You know all about this from
> 5231.) This has been reported several times already.

Yes, I know. But isn't it strange that the standard library is inconsistent
with itself? Shouldn't decisions like "remove a function which other parts of
library expect to be" be more deliberate? I haven't seen such problems in any
of the languages I used, and I think it is not good for the language itself to
have them.

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to