You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It will be very good when this will be fixed. There are some additional points to be considered:
If I remember correctly, the floating point standard allows for both short ("inf") and long ("infinity") syntax.
Are you aware of the other float formatting related issues? I think there used to be a floating point literal parsing problem in rustc for very large literals (not fitting into 32 bits) that is related (can't find the issue right now).
Besides adding support for NaN and inf in from_str/to_str, I personally think rust should define a literal syntax for these, i.e. the compiler should support them directly.
Activity
boggle commentedon Apr 8, 2012
It will be very good when this will be fixed. There are some additional points to be considered:
If I remember correctly, the floating point standard allows for both short ("inf") and long ("infinity") syntax.
Are you aware of the other float formatting related issues? I think there used to be a floating point literal parsing problem in rustc for very large literals (not fitting into 32 bits) that is related (can't find the issue right now).
Besides adding support for NaN and inf in from_str/to_str, I personally think rust should define a literal syntax for these, i.e. the compiler should support them directly.
brson commentedon Apr 9, 2012
If this is standard behavior for converting from strings than I say go for it.
boggle commentedon Apr 9, 2012
More things to check
boggle commentedon Apr 10, 2012
The last one is discusses in #1433. The real kicker would be if all this were supposed by the parser as literal syntax.
brson commentedon Apr 14, 2012
Fixed by 6b5731e
Auto merge of rust-lang#2165 - saethlin:more-clocks, r=RalfJung
Store failure reason into assess metadata (rust-lang#2166)
Merge rust-lang#2165