• deegeese@sopuli.xyz
    link
    fedilink
    arrow-up
    15
    ·
    7 hours ago

    If you’re using a library to handle deserialization , the ugliness of the serial format doesn’t matter that much.

    Just call yaml.load() and forget about it.

    • BodilessGaze@sh.itjust.works
      link
      fedilink
      arrow-up
      3
      ·
      5 hours ago

      That works until you realize your calculations are all wrong due to floating point inaccuracies. YAML doesn’t require any level of precision for floats, so different parsers on a document may give you different results.

      • deegeese@sopuli.xyz
        link
        fedilink
        arrow-up
        3
        ·
        4 hours ago

        What text based serialization formats do enforce numeric precision?

        AFAIK it’s always left up to the writer (serializer)

        • BodilessGaze@sh.itjust.works
          link
          fedilink
          arrow-up
          4
          ·
          edit-2
          4 hours ago

          Cuelang: https://cuelang.org/docs/reference/spec/#numeric-values

          Implementation restriction: although numeric values have arbitrary precision in the language, implementations may implement them using an internal representation with limited precision. That said, every implementation must:

          • Represent integer values with at least 256 bits.
          • Represent floating-point values with a mantissa of at least 256 bits and a signed binary exponent of at least 16 bits.
          • Give an error if unable to represent an integer value precisely.
          • Give an error if unable to represent a floating-point value due to overflow.
          • Round to the nearest representable value if unable to represent a floating-point value due to limits on precision. These requirements apply to the result of any expression except for builtin functions, for which an unusual loss of precision must be explicitly documented.