Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Delete Signedness #4

Open
jamesdbrock opened this issue Jun 1, 2022 · 0 comments
Open

Delete Signedness #4

jamesdbrock opened this issue Jun 1, 2022 · 0 comments

Comments

@jamesdbrock
Copy link
Member

foreign import data Signedness :: Type

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant