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.

Sign up for GitHub

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

Jump to bottom

Should Int in JSNum (Text.Canonical.JSON) really be Int32? #141

Closed
edsko opened this issue Jan 6, 2016 · 2 comments
Closed

Should Int in JSNum (Text.Canonical.JSON) really be Int32? #141

edsko opened this issue Jan 6, 2016 · 2 comments
Labels
hackage-security priority: low (ideal world)
Milestone
Phase 1

Comments

@edsko
Copy link
Contributor

edsko commented Jan 6, 2016

Int is platform dependent and may lead to subtle inconsistencies, in principle; Int64 is actually more than JavaScript values can really represent, as JS uses Double to represent integers.
@edsko edsko added this to the Phase 1 milestone Jan 6, 2016
@edsko
Copy link
Contributor Author

edsko commented Jan 6, 2016

Pinging @dcoutts .

@edsko
Copy link
Contributor Author

edsko commented Jan 6, 2016

This will be closed in #142.

@edsko edsko closed this as completed Jan 6, 2016
@edsko edsko mentioned this issue Jan 6, 2016
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
hackage-security priority: low (ideal world)
Projects
None yet
Milestone
Phase 1
Development

No branches or pull requests
1 participant
@edsko