Incorrect rejection of non-top-level undefined declarations

[gibson042]

There are details at tc39/test262#4332 , but the summary is that QuickJS incorrectly rejects as invalid attempts to create scoped declarations named undefined.

For example, this should print "START" and then "PASS", but instead throws a SyntaxError before anything happens (which is only warranted when such a declaration appears at the top-level scope):

print('START');
{
  const undefined = 1;
  print(undefined === 1 ? 'PASS' : 'FAIL');
}

It may also be worth noting that the analogous NaN and Infinity cases are handled correctly.

[chqrlie]

Hi @gibson042,

This is a bug and we shall fix it, but it is sad to see how many special cases need to be handled explicitly to emulate side effects of historical implementations in useless corner cases.

Thank you for this report.

[bnoordhuis]

The test case passes with quickjs-ng, I believe due to commit quickjs-ng/quickjs@dfe5675