You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
YAML 1.1 allowed numeric literals, i.e. ints and floats, to include underscores, which were semantically ignored. They could thus be used for digit grouping in long values, much as commas are often used as thousands-separators in human-readable text. This was very convenient, and greatly improved readability for large values.
YAML 1.2.0 dropped this feature, for no reason I can find documented anywhere.
I propose that YAML 1.3 bring this feature back.
The text was updated successfully, but these errors were encountered:
I believe the reason is so that the regular expressions for implicit resolution of !int and !float match the JSON rules, since the aim of YAML 1.2 was to be a strict superset of JSON.
YAML 1.1 allowed numeric literals, i.e. ints and floats, to include underscores, which were semantically ignored. They could thus be used for digit grouping in long values, much as commas are often used as thousands-separators in human-readable text. This was very convenient, and greatly improved readability for large values.
YAML 1.2.0 dropped this feature, for no reason I can find documented anywhere.
I propose that YAML 1.3 bring this feature back.
The text was updated successfully, but these errors were encountered: