Add support for ES2022? #40
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi,
Thanks for your great work. It really helps a lot.
Maybe just a question, will you support ES2022 and future ES versions?
Which specific types of syntax are you looking to get support for?
Currently no.
Just a question regarding whether you'll follow up on the updates in ECMAScript.
After all, it's not easy if keeping updating. Or maybe the syntax doesn't change a lot during updates.
Anyway, thanks for your great work.
What I'm trying to understand is why you think that I'm not following updates and why you think this grammar is targeting ES2022 specifically.
Because I see this in the readme.
And you know there're many versions of javascript
So, I'm wondering how do you handle the support for different ECMAScript versions.
According what you said I assume you'll support the latest syntax for ECMAScript?
So, here comes another question will you also support old versions of ECMAScript syntax in case one day someone post a syntax issue in old version like ES2015? For example,
asyncis not supported in ES2015.Anyway, thanks a lot for the response and great work!
Oh, indeed, that reference in the readme is outdated. The grammar is kept up to date with new JS features. Since extensions to the language tend to be defined in a way that doesn't break old code, and Lezer grammars aren't very usable as validators anyway, no effort is made to support parsing only an old subset of the language.