# What's the accepted way to ensure same integer behavior between 32-bit and 64-bit Julia?

**URL:** <https://discourse.julialang.org/t/whats-the-accepted-way-to-ensure-same-integer-behavior-between-32-bit-and-64-bit-julia/49564>\
**Category:** General Usage\
**Created:** [November 4, 2020, 4:09am UTC](https://discourse.julialang.org/t/whats-the-accepted-way-to-ensure-same-integer-behavior-between-32-bit-and-64-bit-julia/49564 "2020-11-04T04:09:10Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**Author:** ![rfourquet](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/rfourquet/32/3610_2.png) [@rfourquet](https://discourse.julialang.org/u/rfourquet)\
**Post date:** [November 7, 2020, 8:32pm UTC](https://discourse.julialang.org/t/whats-the-accepted-way-to-ensure-same-integer-behavior-between-32-bit-and-64-bit-julia/49564/21 "2020-11-07T20:32:20Z")

</div>

Thank you very much! this seems indeed to work as expected.

> [@Benny](#):
>
> if you want to make `literals_swapper` public for the same purpose, then I’d find it convenient to have the option to give no argument to get `@swapliterals` 's default `BigInt` behavior.

Ah yes, that’s a good idea. I don’t see an obstacle to making `literals_swapper` public, but I just need to think a bit about it, and also how to call it (maybe the current name is fine though).

[Previous page](https://discourse.julialang.org/t/whats-the-accepted-way-to-ensure-same-integer-behavior-between-32-bit-and-64-bit-julia/49564.md?page=1)
