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
When running this code, the output is 42, not +4.200000e+001 as expected when an integer is converted to a float32. This seems to be a bug in the handling of FloatKind value conversion.
The text was updated successfully, but these errors were encountered:
As mentioned in #1377, I don't think striving for compatibility with Go's println is a useful endeavour, as the documentation for Go's println specifically says that it is implementation-specific.
If you can think of a good argument of why this should be the case -- or anyone reading this agrees that we should try to have println/print work in the same way as Go's format and can make a good argument for it, please reopen (or ask to reopen) this issue and make your case.
Personally, I think we'll obviously strive for 100% compatibility when we have the language-defined fmt.Println, but println seems like a non-goal. :)
Description
When running this code, the output is 42, not +4.200000e+001 as expected when an integer is converted to a float32. This seems to be a bug in the handling of FloatKind value conversion.
The text was updated successfully, but these errors were encountered: