-
Notifications
You must be signed in to change notification settings - Fork 910
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
Remove UnsafeBeyond2Pow53Minus1
type suffixes
#3456
Conversation
🦋 Changeset detectedLatest commit: 42214f5 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
7647088
to
b02834e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
b02834e
to
42214f5
Compare
Because there has been no activity on this PR for 14 days since it was merged, it has been automatically locked. Please open a new issue if it requires a follow up. |
Both RPC and RPC Subscriptions packages now use custom JSON serialization to safely convert large integers as
bigints
from the server requests/responses. This means we are no longer handlingbigints
that are unsafe below2^53-1
which also means we can remove theUnsafeBeyond2Pow53Minus1
suffixes to all types currently using it.Note that the
F64UnsafeSeeDocumentation
type is excluded from this refactoring as the bigint serialization only affects integers.