-
-
Notifications
You must be signed in to change notification settings - Fork 492
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
refactor(semantic)!: remove SymbolFlags::Export
#7414
refactor(semantic)!: remove SymbolFlags::Export
#7414
Conversation
Your org has enabled the Graphite merge queue for merging into mainAdd the label “0-merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix. You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link. |
SymbolFlags::Export
SymbolFlags::Export
SymbolFlags::Export
CodSpeed Performance ReportMerging #7414 will not alter performanceComparing Summary
|
Merge activity
|
close: #7338 close: #7344 The `SymbolFlags::Export` is Initially used to solve `ExportSpecifier` that is not `IdentifierReference` that causes we cannot determine whether a Binding is not used everywhere by `Semantic`. Since #3820 this problem is solved, so we don't need `SymbolFlags::Export` no longer. Also, removing this can help us easier to pass the `Semantic` check in `Transformer`
32228c2
to
c90537f
Compare
338571d
to
27b2268
Compare
close: #7338
close: #7344
The
SymbolFlags::Export
is Initially used to solveExportSpecifier
that is notIdentifierReference
that causes we cannot determine whether a Binding is not used everywhere bySemantic
.Since #3820 this problem is solved, so we don't need
SymbolFlags::Export
no longer. Also, removing this can help us easier to pass theSemantic
check inTransformer