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
TEST(WTF, BigInteger) {
nlohmann::json val = -3383556239975101330LL;
val = nlohmann::json::parse(val.dump());
EXPECT_EQ(-3383556239975101330, val.get<int64_t>());
}
And this is the internal inconsistency.
As far as I know, RFC does not require JSON integers to be in any range.
I think that internal consistency is more important than possible non-interoperability with third-party JSON parsers.
The text was updated successfully, but these errors were encountered:
Currently the test below fails:
And this is the internal inconsistency.
As far as I know, RFC does not require JSON integers to be in any range.
I think that internal consistency is more important than possible non-interoperability with third-party JSON parsers.
The text was updated successfully, but these errors were encountered: