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
Hello,
Currently the documentation says about json_int_t that "It represents the widest integer type available on your system." So by definition it's supposed to be equivalent to intmax_t. However, long long is not guaranteed to be equivalent to intmax_t. We should simply typedef json_int_t as an alias to intmax_t and forget about the nonsense of whether it's a long or long long.
The text was updated successfully, but these errors were encountered:
Hello,
Currently the documentation says about
json_int_t
that "It represents the widest integer type available on your system." So by definition it's supposed to be equivalent tointmax_t
. However,long long
is not guaranteed to be equivalent tointmax_t
. We should simply typedefjson_int_t
as an alias tointmax_t
and forget about the nonsense of whether it's along
orlong long
.The text was updated successfully, but these errors were encountered: