Why is strict_div implemented in terms of overflowing_div for signed integers?

Your question doesn't seem to be answered here:

github.com/rust-lang/rust

Implement strict integer operations that panic on overflow (#116090)

master ← rmehri01:strict_integer_ops

opened 04:50AM - 23 Sep 23 UTC

        rmehri01
      

+996 -15

This PR implements the first part of the ACP for adding panic on overflow style …arithmetic operations (https://github.com/rust-lang/libs-team/issues/270), mentioned in #116064. It adds the following operations on both signed and unsigned integers: - strict_add - strict_sub - strict_mul - strict_div - strict_div_euclid - strict_rem - strict_rem_euclid - strict_neg - strict_shl - strict_shr - strict_pow Additionally, signed integers have: - strict_add_unsigned - strict_sub_unsigned - strict_abs And unsigned integers have: - strict_add_signed The div and rem operations are the same as normal division and remainder but are added for completeness similar to the corresponding wrapping_* operations. I'm not sure if I missed any operations, I basically found them from the wrapping_* and checked_* operations on both integer types.

And I can't think of a good reason.