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

*: Fix integer types #248

Merged
merged 1 commit into from
Jul 6, 2022
Merged

*: Fix integer types #248

merged 1 commit into from
Jul 6, 2022

Conversation

fyrchik
Copy link
Contributor

@fyrchik fyrchik commented Jul 6, 2022

When using contracts as a dependency, out-of-range int can cause
problems on 32-bit architectures. Contract byte-code hasn't changed.

Signed-off-by: Evgenii Stratonikov evgeniy@nspcc.ru

When using contracts as a dependency, out-of-range `int` can cause
problems on 32-bit architectures. Contract byte-code hasn't changed.

Signed-off-by: Evgenii Stratonikov <evgeniy@nspcc.ru>
@alexvanin
Copy link
Contributor

I doubt 32-bit architecture is going to appear on high-load server hardware. But some light-weight clients and proxy nodes might be running on raspberries.

@fyrchik fyrchik merged commit 69b308e into nspcc-dev:master Jul 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants