-
Notifications
You must be signed in to change notification settings - Fork 664
fix(1374): support declaration emit for expando functions #1399
New issue
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
Conversation
698d40d
to
c063ac4
Compare
...elines/reference/submodule/compiler/declarationEmitDefaultExportWithStaticAssignment.js.diff
Outdated
Show resolved
Hide resolved
testdata/baselines/reference/submodule/compiler/declarationEmitLateBoundAssignments.js.diff
Outdated
Show resolved
Hide resolved
testdata/baselines/reference/submodule/compiler/declarationEmitFunctionKeywordProp.js.diff
Show resolved
Hide resolved
testdata/baselines/reference/submodule/compiler/declarationEmitLateBoundJSAssignments.js.diff
Show resolved
Hide resolved
...ata/baselines/reference/submodule/compiler/jsxDeclarationsWithEsModuleInteropNoCrash.js.diff
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like a pretty straight port of the logic from strada - @sandersn should weigh in on weather he thinks that's right. I do not recall if these is one of the constructs that changed meaningfully in the js reparser rewrite and, thus, should also have it's declaration emit logic adjusted, too.
Expandos didn't fundamentally change, but they are losing a lot of their complicated features. So the core changes to emit might be right-ish, but you won't need to reintroduce any code in the parser or binder, I think. |
@sandersn Thanks for the clarification. |
No description provided.