Change documentation of modInverse to not specify error thrown.

sdk/lib/core/int.dart

Index: sdk/lib/core/int.dart
diff --git a/sdk/lib/core/int.dart b/sdk/lib/core/int.dart
index 58d80b84607f5eec6965c1030ef417f6f4cc6cd5..16a1e0779db177679a66e9d6bc7b6dabc6104bc6 100644
--- a/sdk/lib/core/int.dart
+++ b/sdk/lib/core/int.dart
@@ -116,7 +116,7 @@ abstract class int extends num {
    * modulo [modulus].
    *
    * The [modulus] must be positive.
-   * Throws a RangeError if no modular inverse exists.
+   * Throws if no modular inverse exists.

[regis, 2015/06/24 18:29:54]

For consistency, "It is an error if ..." would have been better.

[Lasse Reichstein Nielsen, 2015/06/30 12:39:15]

True.
I haven't yet decided on whether it should be documented which error it throws
in this case. It's not generally something the user can detect before calling,
so they need to catch the error. For that reason we might want to specify which
error object is thrown.
The actual error would probably be UnsupportedError (ArgumentError could be
argued, but it's not that the argument is bad, it just that there is no solution
to the question you are asking, RangeError doesn't fit). Maybe we should even
have an ArithmeticException - because its something the user will want to catch,
so it should be an exception.

Or we could just return 0, which is never a valid inverse.

    */
   int modInverse(int modulus);