ModInverse is defined for all values of g, and for positive and negative values n, but not for a zero n.
ModInverse sets z to the multiplicative inverse of g in the ring ℤ/nℤ
and returns z. If g and n are not relatively prime, g has no multiplicative
inverse in the ring ℤ/nℤ. In this case, z is unchanged and the return value
is nil.
The ring of numbers modulo zero does not exist, and being coprime with zero is meaningless, so the current docs don't cover it.
Arguably, ModInverse should always panic when the modulo is zero, but currently it returns nil for g > 1, returns 1 for g = 1, returns nil for g = 0, and panics for g < 0. Turning a non-panic into a panic for the sake of consistency is asking for trouble, so we should just make it return nil consistently for n = 0.
This could break programs that try to dereference the return value of ModInverse(1, 0), but that feels like a specific enough condition that programs won't have come to rely on it #famouslastwords.
The text was updated successfully, but these errors were encountered:
This issue is marked for Go1.18, but the CL was marked with "Wait-Release". Shall we roll this over to Go1.19 or should we make the breaking change to return nil if the modulus is zero. Now one reservation here is that the internal code has a comment that its internal implementation of GCD expects the parameters to be > 0. Should we perhaps instead document this issue or just wait until Go1.19. What do you think @griesemer@ianlancetaylor?
Alright, I shall make the call to move this to the Go1.19 milestone as per the CL labelling and given that it is quite late in the cycle for a breakiing change.
ModInverse is defined for all values of g, and for positive and negative values n, but not for a zero n.
The ring of numbers modulo zero does not exist, and being coprime with zero is meaningless, so the current docs don't cover it.
Arguably, ModInverse should always panic when the modulo is zero, but currently it returns nil for g > 1, returns 1 for g = 1, returns nil for g = 0, and panics for g < 0. Turning a non-panic into a panic for the sake of consistency is asking for trouble, so we should just make it return nil consistently for n = 0.
This could break programs that try to dereference the return value of ModInverse(1, 0), but that feels like a specific enough condition that programs won't have come to rely on it #famouslastwords.
The text was updated successfully, but these errors were encountered: