News for hackers. Stuff that matters.

A comment on Go 2, here we come. Parent comment

Re:Go 2, here we come by benhoyt on Friday November 30, 2018 @08:31AM (#18568914)
Odd, I've rarely had this issue, and almost never need to do complicated math on the index of a range (maybe "multiply by two and add one" kind of stuff, but nothing from the "math" pkg). Also, note that the math.* functions all use float64, not in64.
[ Parent | on HN ]
Re:Go 2, here we come by LanceH on Friday November 30, 2018 @11:02AM (#18569997)
Yes, you're right float64 in the math package. So I've definitely run into this with float vs float64.

As for the int vs int64, I definitely run into what I describe on Project Euler. Probably using a self referential map[int]int when I need to suddenly pull an int64 and everything gets infected.

I realize it's just a matter of convenience for me, but I personally have no downside to int == int64.

[ Parent | on HN ]