Currently Decimal128 raises InvalidRange for two distinct conditions: the value given to Decimal128 is out of range, and the value contains too much precision. The second situation should utilize its own exception class (which will be derived from InvalidRange for now for backwards compatibility) so that the situation is clearly communicated to the users.