Length.Zero.Inverse() returns ReciprocalLength.Zero (v6)

[lipchev]

Since the release/v6 supports NaN and PositiveInfinity I think it would make sense for:

        [Theory]
        [InlineData(-1.0, -1.0)]
        [InlineData(-2.0, -0.5)]
        [InlineData(0.0, 0.0)]
        [InlineData(1.0, 1.0)]
        [InlineData(2.0, 0.5)]
        public static void InverseReturnsReciprocalLength(double value, double expected)
        {
            var length = new Length(value, LengthUnit.Meter);
            var inverseLength = length.Inverse();

            Assert.Equal(expected, inverseLength.InverseMeters);
        }

to be changed to:

        [Theory]
        [InlineData(-1.0, -1.0)]
        [InlineData(-2.0, -0.5)]
        [InlineData(0.0, double.PositiveInfinity)]
        [InlineData(1.0, 1.0)]
        [InlineData(2.0, 0.5)]
        public static void InverseReturnsReciprocalLength(double value, double expected)
        {
            var length = new Length(value, LengthUnit.Meter);
            var inverseLength = length.Inverse();

            Assert.Equal(expected, inverseLength.InverseMeters);
        }

[angularsen]

Sounds good, as long as we're all in on double now. We'll just have to revisit if and when we introduce other number types again.

[lipchev]

Sounds good, as long as we're all in on double now. We'll just have to revisit if and when we introduce other number types again.

Here's how I currently represent these:

    /// <summary>
    ///     The value representing the positive infinity.
    /// </summary>
    public static QuantityValue PositiveInfinity { get; } = new(BigInteger.One, BigInteger.Zero);

    /// <summary>
    ///     The value representing the negative infinity.
    /// </summary>
    public static QuantityValue NegativeInfinity { get; } = new(BigInteger.MinusOne, BigInteger.Zero);

    /// <summary>
    ///     The value representing the result of dividing zero by zero.
    /// </summary>
    public static QuantityValue NaN { get; } = new(BigInteger.Zero, BigInteger.Zero);