The v3.2.3 revision allows passing in float with no precision argument into the BigDecimal initializer.
This allows values that were previously invalid to now be considered valid. In cases where BigDecimal is being used in validation systems or serialization - this is an API breaking change.
I assume BigDecimal uses semver as it uses a 3 digit version - the major version should be increased to v4.
See message thread in #314 for some more context
The v3.2.3 revision allows passing in float with no precision argument into the BigDecimal initializer.
This allows values that were previously invalid to now be considered valid. In cases where BigDecimal is being used in validation systems or serialization - this is an API breaking change.
I assume BigDecimal uses semver as it uses a 3 digit version - the major version should be increased to v4.
See message thread in #314 for some more context