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
Int64 is massively overkill for golang points, so there's no reason we need to continue using int64. Oversight on my part when I originally created the struct.
The text was updated successfully, but these errors were encountered:
Currently point uses int64. This is overkill and also makes iteration more annoying: https://stackoverflow.com/questions/34811167/can-i-make-the-index-int64-in-golangs-for-range-iteration
Int64 is massively overkill for golang points, so there's no reason we need to continue using int64. Oversight on my part when I originally created the struct.
The text was updated successfully, but these errors were encountered: