It's undefined behavior, but what exactly you think will happen if that occurs?
The result will still be an int32_t which is either in range or not, which can
happen without invoking any undefined behavior and which we need to catch.
So what exactly is this supposed to achieve?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1502#issuecomment-762043370
_______________________________________________
Rpm-maint mailing list
[email protected]
http://lists.rpm.org/mailman/listinfo/rpm-maint
