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
I'd expect x to be Int32 here, and the fact that it's not means that I need to wrap all sorts of stuff in int32; that's probably not even sufficient if I don't break down every expression so that it only has one operator, otherwise I'll still have internal Int64s floating around in something like int32((a + b) * c).
@astrieanna mentioned that there's probably already a bug on this, but neither of us could find it.
The text was updated successfully, but these errors were encountered:
There has been lots of discussion on this, and lots of us think the behaviour is wrong (and that it should be changed). It is at least mentioned in the FAQ, but not as prominent as it should.
I'd expect x to be Int32 here, and the fact that it's not means that I need to wrap all sorts of stuff in
int32
; that's probably not even sufficient if I don't break down every expression so that it only has one operator, otherwise I'll still have internal Int64s floating around in something likeint32((a + b) * c)
.@astrieanna mentioned that there's probably already a bug on this, but neither of us could find it.
The text was updated successfully, but these errors were encountered: