You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I came across a use case involving merging multiple parsed objects that should all be bit64::integer64s, but some of the objects don't contain any values exceeding the INT_MAX threshold (meaning they were downcasted to R's regular 32-bit integers).
Adding an "always" option to int64_policy= that forces all integers to be returned as bit64::integer64s will eliminate this post-parse processing hassle.
The text was updated successfully, but these errors were encountered:
I came across a use case involving merging multiple parsed objects that should all be
bit64::integer64
s, but some of the objects don't contain any values exceeding theINT_MAX
threshold (meaning they were downcasted to R's regular 32-bit integers).Adding an
"always"
option toint64_policy=
that forces all integers to be returned asbit64::integer64
s will eliminate this post-parse processing hassle.The text was updated successfully, but these errors were encountered: