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
The lines complaining about Inf overflow should go (they're confusing, there's no Inf in the code).
It should be enough to avoid overwriting the original Node's Val in case of overflow in truncfltlit( ) (like we already do in the recently committed trunccmplxlit( )).
The text was updated successfully, but these errors were encountered:
…flow
Also adjust truncfltlit to make it more similar to trunccmplxlit, and
make it report an error for bad Etypes.
Fixesgolang#19947
Change-Id: I6684523e989c2293b8a8e85bd2bfb9c399c5ea36
Reviewed-on: https://go-review.googlesource.com/40453
Reviewed-by: Robert Griesemer <gri@golang.org>
go version devel +746441f97f Wed Apr 12 18:16:41 2017 +0000 linux/amd64
Consider the following:
on tip (1.8 too) we get a double error on the first two lines (but not on the last two):
The lines complaining about
Inf
overflow should go (they're confusing, there's noInf
in the code).It should be enough to avoid overwriting the original Node's
Val
in case of overflow intruncfltlit( )
(like we already do in the recently committedtrunccmplxlit( )
).The text was updated successfully, but these errors were encountered: