-
-
Notifications
You must be signed in to change notification settings - Fork 482
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
feat(ast_codegen): add #[visit(enter_before)]
hint.
#4147
feat(ast_codegen): add #[visit(enter_before)]
hint.
#4147
Conversation
Your org has enabled the Graphite merge queue for merging into mainAdd the label “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. |
This stack of pull requests is managed by Graphite. Learn more about stacking. |
CodSpeed Performance ReportMerging #4147 will not alter performanceComparing Summary
|
Please see #4142 (comment). I'm not clear why this change is required. |
I just saw your comment, Even with that it is a good thing to have the |
@Dunqing do you know about the semantic details here? |
163f302
to
9abe2d8
Compare
|
Yes, I think we can keep the |
Personally, I don't think we should ever enter the node late. It is just confusing, and I can't see a use case. If you want to avoid throwing away the generator code you already wrote, by all means merge it in, but would you consider "deactivating" |
I'll generate an error on encountering it for now. |
9abe2d8
to
a792c3f
Compare
decorators
in Class
before node events.#[visit(enter_before)]
hint.
81cb539
to
ee42fed
Compare
Merge activity
|
Closes #4142 I can split it into 2 PRs but it seems pointless. Let me know if you guys disagree with me.
ee42fed
to
3ba7cfe
Compare
Closes #4142
I can split it into 2 PRs but it seems pointless. Let me know if you guys disagree with me.