Skip to content
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

Unify AST Visitors with a macro like MIR Visitors #128974

Open
wants to merge 145 commits into
base: master
Choose a base branch
from

Conversation

maxcabrajac
Copy link

This is WIP PR to work on #127615

@rustbot
Copy link
Collaborator

rustbot commented Aug 11, 2024

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @lcnr (or someone else) some time within the next two weeks.

Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (S-waiting-on-review and S-waiting-on-author) stays updated, invoking these commands when appropriate:

  • @rustbot author: the review is finished, PR author should check the comments and take action accordingly
  • @rustbot review: the author is ready for a review, this PR will be queued again in the reviewer's queue

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Aug 11, 2024
@rust-log-analyzer

This comment has been minimized.

@cjgillot cjgillot self-assigned this Aug 11, 2024
@lcnr
Copy link
Contributor

lcnr commented Aug 12, 2024

r? compiler

@rustbot rustbot assigned davidtwco and unassigned cjgillot and lcnr Aug 12, 2024
@lcnr
Copy link
Contributor

lcnr commented Aug 12, 2024

r? @cjgillot woops

@rustbot rustbot assigned cjgillot and unassigned davidtwco Aug 12, 2024
@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

Copy link
Contributor

@cjgillot cjgillot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wow, that's some great work you did @maxcabrajac!
Please take this as an opportunity to simplify stuff. If some distinction has you make weird corner cases, don't hesitate to remove it. My comments are suggestions in this direction.

compiler/rustc_ast/src/visitors.rs Outdated Show resolved Hide resolved
compiler/rustc_ast/src/visitors.rs Outdated Show resolved Hide resolved
compiler/rustc_ast/src/visitors.rs Outdated Show resolved Hide resolved
Comment on lines 320 to 325
make_visit!{P!(Local), visit_local, walk_local}
make_visit!{P!(Pat), visit_pat, walk_pat}
make_visit!{P!(Expr), visit_expr, walk_expr}
make_visit!{P!(Ty), visit_ty, walk_ty}
make_visit!{P!(Block), visit_block, walk_block}
make_visit!{P!(FnDecl), visit_fn_decl, walk_fn_decl}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we remove the P! from all these?

Copy link
Author

@maxcabrajac maxcabrajac Aug 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I put these P! to maintain all function signatures the same, thus avoiding changes on implementers. I don't know why the original MutVisitor received &mut P<T> instead of &mut T for these types, but I just kept what was being done.

@maxcabrajac
Copy link
Author

I think it's better to do two passes. Do what can be done without changing the trait API, after that, change what is weird about their original implementation and change all implementers accordingly. What do you think about it?
There is a pretty big roadblock now... Everything around walk_item seems to be pretty different from Visitor to MutVisitor and I really don't know where to start =/. Do you have any advice on that?

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants