We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
~~
See tc39/ecma262#2418 (comment). As part of this patch, we define a grammar that includes ~~:
<emu-grammar type="definition"> ClassSetReservedDoublePunctuator :: one of `&&` `!!` `##` `$$` `%%` `**` `++` `,,` `..` `::` `;;` `<<` `==` `>>` `??` `@@` `^^` ```` `~~` </emu-grammar>
It seems esmeta doesn’t like this for some reason. The check fails: https://github.com/tc39/ecma262/actions/runs/5088350689/jobs/9144652112?pr=2418#step:7:1
Run "${ESMETA_HOME}"/bin/esmeta tycheck -status -tycheck:log -tycheck:ignore=esmeta-ignore.json ======================================== extract phase ---------------------------------------- [ESMeta v0.3.0] [Parser (List[spec.Production])] [2[8](https://github.com/tc39/ecma262/actions/runs/5088350689/jobs/9144652112?pr=2418#step:7:9).[12](https://github.com/tc39/ecma262/actions/runs/5088350689/jobs/9144652112?pr=2418#step:7:13)] failure: end of input expected `~~` ^ Error: Process completed with exit code 1.
@bakkot said:
No idea what's up with that one; probably an esmeta bug. We'll turn the check off or fix esmeta before merging
It would be great if this could be fixed in esmeta.
The text was updated successfully, but these errors were encountered:
v
Fixed bugs in Spec parser for terminals (#145)
f244aa6
26976c5
Hi, @mathiasbynens. Thanks for your kind report on the bugs in the current version of ESMeta. Since I fixed this issue in #146, I closed this issue.
Sorry, something went wrong.
No branches or pull requests
See tc39/ecma262#2418 (comment). As part of this patch, we define a grammar that includes
~~
:It seems esmeta doesn’t like this for some reason. The check fails: https://github.com/tc39/ecma262/actions/runs/5088350689/jobs/9144652112?pr=2418#step:7:1
@bakkot said:
It would be great if this could be fixed in esmeta.
The text was updated successfully, but these errors were encountered: