Number.ResidueClass.Check

The best solution seems to let modulus be part of the type. This could happen with a phantom type for modulus and a run function like runST. Then operations with non-matching moduli could be detected at compile time and zero and one could be generated with the correct modulus. An alternative trial can be found in module ResidueClassMaybe.

r /: m is the residue class containing r with respect to the modulus m

Check if two residue classes share the same modulus