true and false are treated as names

[Rich-Harris]

REPL — this template...

<label>
  <input type='radio' bind:group='foo' value='{{false}}'> input
</label>

<label>
  <input type='radio' bind:group='foo' value='{{true}}'> output
</label> 

...ends up like this:

var last_input_value = root.false;

This was probably introduced by #385. I'd argue that true, false, null and maybe undefined should not get the same treatment as class et al.

[Rich-Harris]

Note: you can workaround this by adding 'false': false, 'true': true to your data....

[Conduitry]

Yeah this is definitely from #385. If we want to keep that behavior, instead of having special cases for certain names (true, `false, etc), maybe we could first try parsing, and then if that failed and we were a single all-lowercase word do the special case for the identifier ... otherwise report the parse failure.