Open zkat opened 5 months ago
I think I'm 100% neutral on this. Like, CSS is case-insensitive with its keywords, but also anyone who writes COLOR: Red;
deserves jail.
But I also suspect I'll naturally try to spell it #NaN
, and sometimes people like #TRUE
to make them stand out more, so eh.
I feel like these alternatives are mainly just things that people are going to want to write linter rules against. But I had the same feeling about quote-less strings, and maybe alternatives are fine.
Similar to the "I'll probably type #NaN
" thing, depending on whether I've been most recently writing Python or JS my fingers naturally spell it True
or true
.
So I guess I'm weakly for making them insensitive (but maybe with a recommendation about using lowercase as the canonical serialization?)
Can/should we make keywords case insensitive? That is,
#true
,#null
,#nan
, etc.