During the past year there were a lot of checks added to detect out of bounds value (reported by fuzzing and static analysis) because they can have unexpected behaviour as per C specs and may result in security issues, although some compilers/architectures handle them smoothly. The changes were done in the common functions located in the core.

In this particular case, it makes checks that the value is in between INT_MIN and INT_MAX (which should be -2147483648 and 2147483647).

Maybe it would be better to understand what you need and decide what is the better option for it. The example is like converting string to int and then the resulting int back to string in order to print it, which sounds useless, but can be just as an example here.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.