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 thing of it is, the foreign JavaScript Long object stores an unsigned boolean flag which indicates whether or not the integer is signed or unsigned. Therefore this type-level Signedness is redundant, because that information is always available at runtime by inspecting the unsigned flag.
The unsigned flag is stupid and the long.js authors should have left it out and kept that information at the type level with something like the Signedness parameter. But that's not how things work in JavaScript world.
The text was updated successfully, but these errors were encountered:
purescript-int64/src/Data/Int64/Internal.purs
Line 113 in 6cba8be
The thing of it is, the foreign JavaScript
Long
object stores anunsigned
boolean flag which indicates whether or not the integer is signed or unsigned. Therefore this type-levelSignedness
is redundant, because that information is always available at runtime by inspecting theunsigned
flag.The
unsigned
flag is stupid and the long.js authors should have left it out and kept that information at the type level with something like theSignedness
parameter. But that's not how things work in JavaScript world.The text was updated successfully, but these errors were encountered: