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
Right now the reference encoder feels free to sort parameter bindings lexicographically, which doesn't play nicely with engines.
The text was updated successfully, but these errors were encountered:
What's the problem, exactly? Default arguments?
Sorry, something went wrong.
@efaust Is this still a problem? Do you want me to do something about this?
AssertedPositionalParameterName
CheckParameterNames checks the order in step 5: https://binast.github.io/ecmascript-binary-ast/#sec-checkparameternames
and actualParams has names in the syntactical order: https://tc39.github.io/ecma262/#sec-function-definitions-static-semantics-boundnames
so, if the order doesn't match, it's the reference encoder's bug. I'll check it shortly
moved the issue to binjs-ref. I'd suggest closing this issue.
No branches or pull requests
Right now the reference encoder feels free to sort parameter bindings lexicographically, which doesn't play nicely with engines.
The text was updated successfully, but these errors were encountered: