Inconsistent shared property names for min/max values

Currency has shared MinValue and MaxValue properties, whereas Integer and Double have Min and Max and DateTime has MinValue but not MaxValue or Max.

These should be consistent.

Personally I prefer MinValue and MaxValue as they are clearer.

Implemented this for the next release: https://feedback.objo.dev/feature/1240

Thanks for the suggestion. The standard library now standardises on MinValue and MaxValue as the shared-property names.

What changed

The old Integer/Double spellings still exist, so existing code keeps compiling and running unchanged:

Using the short names now produces a normal deprecation warning that points you at the replacement, for example:

The canonical names produce no warning.

A few deliberate decisions

Double.MinValue is the most negative finite Double and Double.MaxValue is the largest positive finite Double. Double.Infinity remains a separate value.
DateTime.MaxValue is the latest representable date/time (9999-12-31 23:59:59.999). DateTime.Empty is unchanged and is still the recommended way to represent an unset date.
No Currency.Min/Currency.Max or DateTime.Min/DateTime.Max were added - exactly one canonical pair per type.
Maths.Min()/Maths.Max() and Vector2.Min()/Vector2.Max() keep their names: those are methods that select or calculate a value, not boundary constants.
Duration gets no min/max bounds - Duration.Infinite already has its own no-timeout semantics.
The new spellings also work everywhere the old ones did at compile time, including constant expressions such as Duration.FromTicks(Integer.MaxValue \ 2).