Closed mindplay-dk closed 4 years ago
I just thought of a way to further reduce the noise in configuration files and the like.
What if we allowed unquoted string literals?
For example:
{ foo: bar }
That's not a JS feature, but it is JS compatible syntax - it merely presumes bar is a const, which has been predefined with the value "bar".
bar
const
"bar"
Thoughts?
Thanks for the suggestion, but any features that are incompatible with ES5 will not be implemented.
I just thought of a way to further reduce the noise in configuration files and the like.
What if we allowed unquoted string literals?
For example:
That's not a JS feature, but it is JS compatible syntax - it merely presumes
bar
is aconst
, which has been predefined with the value"bar"
.Thoughts?