We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Example:
julia> parse(Int64, " 5 ") 5 julia> parse(FixedDecimal{Int64,2}, " 5.0 ") ERROR: ArgumentError: invalid digit: ' ' julia> parse(FixedDecimal{Int64,2}, "5.0") FixedDecimal{Int64,2}(5.00) julia> parse(Float64, " 3.14 ") 3.14 julia> parse(Float64, " 3 . 14 ") ERROR: ArgumentError: cannot parse " 3 . 14 " as Float64
The text was updated successfully, but these errors were encountered:
That's interesting. I'd personally lean towards parse(Int64, ...) and parse(Float64, ...) not support whitespace
parse(Int64, ...)
parse(Float64, ...)
Sorry, something went wrong.
Hmm, yeah i'm ambivalent. I guess accepting whitespace is also what C++'s parsing functions do as well (io >> x).
io >> x
Given the julia behavior i'd say we should just do the same?
No branches or pull requests
Example:
The text was updated successfully, but these errors were encountered: