search for: interpretdecimal

...or 16! For the recoverable APFloat assertions: assertArithmeticOK: Compile-time arithmetic does not support these semantics readExponent: Exponent has no digits Invalid character in exponent totalExponent: Invalid character in exponent skipLeadingZeroesAndAnyDot: String cannot be just a dot interpretDecimal: Multiple dots in float Invalid character in digit string trailingHexadecimalFraction: Invalid trailing hexadecimal fraction! I'd expect we'd want to keep the assertions that check to make sure we're comparing APInts and APFloats of the right semantics. I'm not sure if it makes...

...hmeticOK: > Compile-time arithmetic does not support these semantics > > readExponent: > Exponent has no digits > Invalid character in exponent > > totalExponent: > Invalid character in exponent > > skipLeadingZeroesAndAnyDot: > String cannot be just a dot > > interpretDecimal: > Multiple dots in float > Invalid character in digit string > > trailingHexadecimalFraction: > Invalid trailing hexadecimal fraction! > > > I'd expect we'd want to keep the assertions that check to make sure > we're comparing APInts and APFloats of the right...