Yes! There is the same ambiguity in Yaml, so syntax highlighters of the format don't agree where a string ends... The site even has an ambiguous example: three: 4 # oops Well, is that "4 # oops" or 4? I saw no rule…
One advantage const can bring (at least when used with primitives or frozen values) can come from JS IDEs: if they detect a value is const, they can report its value when hovering the variable name, in a static way.…
Yes! There is the same ambiguity in Yaml, so syntax highlighters of the format don't agree where a string ends... The site even has an ambiguous example: three: 4 # oops Well, is that "4 # oops" or 4? I saw no rule…
One advantage const can bring (at least when used with primitives or frozen values) can come from JS IDEs: if they detect a value is const, they can report its value when hovering the variable name, in a static way.…