-
Notifications
You must be signed in to change notification settings - Fork 13.6k
resolve: Introduce RibKind::Block
#145065
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
base: master
Are you sure you want to change the base?
Conversation
r? @davidtwco rustbot has assigned @davidtwco. Use |
/// Behaves like `Normal`, but also partially like `Module` if the block contains items. | ||
/// `Block(None)` must be always processed in the same way as `Block(Some(module))` | ||
/// with empty `module`. The module can be `None` only because creation of some definitely | ||
/// empty modules is skipped as an optimization. |
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.
If the optimization is removed, some diagnostics in UI tests still change, but due to other issues, like considering only a single immediate Module
parent instead of walking the chain.
This comment was marked as resolved.
This comment was marked as resolved.
to avoid confusing module items, blocks with items, and blocks without items.
@bors r+ |
resolve: Introduce `RibKind::Block` to avoid confusing module items, blocks with items, and blocks without items. Addresses rust-lang#143141 (comment) and rust-lang#143141 (comment). A couple of related cleanups are also added on top.
to avoid confusing module items, blocks with items, and blocks without items.
Addresses #143141 (comment) and #143141 (comment).
A couple of related cleanups are also added on top.