--- Comment #5 from Kenji Hara <> 2012-09-27 18:29:09 PDT ---
(In reply to comment #3)
> FYI, parse!int also has the same problem. Only floating point types seem to
> behave correctly:

NO, this is just a bug in `T parse!T(input) if (isFloatingPoint!T)`.
The parse function family should not skip leading white spaces implicitly.

I think it is simple, no special cases, and flexible design.

See also my github comment to the pull#817:

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

Reply via email to