i understand, but think that since Go particularly allows these conversations transparently, consistency should be covered by language specification. it potentially causes bugs that doesn't fail fast, didn't for me anyway.
how much code out there would break if you changed the existing returned value on x86? On Wednesday, 8 July 2020 18:37:03 UTC+1, Kurtis Rader wrote: > > > The result of what you're doing is undefined. You might as well be > executing the HCF instruction. See > https://stackoverflow.com/questions/10366485/problems-casting-nan-floats-to-int > for > one reasonably good discussion. You absolutely have to special-case NaN if > it can be an input to your code. You should not assume it will be converted > to a particular int value. > > -- > Kurtis Rader > Caretaker of the exceptional canines Junior and Hank > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/a15d1ee7-361e-42f5-9ece-fb8209f0a93co%40googlegroups.com.
