rust/compiler/rustc_resolve/src/late, branch masterhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=master2025-09-28T21:33:34+00:00Detect unconstructable re-exported tuple structs2025-09-28T21:33:34+00:00Esteban Küberesteban@kuber.com.ar2024-11-25T21:52:08+00:00urn:sha1:8f7d61b9efe1f44701f87fe4647eb1f39d20f434
When a tuple-struct is re-exported that has inaccessible fields at the `use` scope, the type's constructor cannot be accessed through that re-export. We now account for this case and extend the resulting resolution error. We also check if the constructor would be accessible directly, not through the re-export, and if so, we suggest using the full path instead.
```
error[E0423]: cannot initialize a tuple struct which contains private fields
--> $DIR/ctor-not-accessible-due-to-inaccessible-field-in-reexport.rs:12:33
|
LL | let crate::Foo(x) = crate::Foo(42);
| ^^^^^^^^^^
|
note: the type is accessed through this re-export, but the type's constructor is not visible in this import's scope due to private fields
--> $DIR/ctor-not-accessible-due-to-inaccessible-field-in-reexport.rs:3:9
|
LL | pub use my_mod::Foo;
| ^^^^^^^^^^^
help: the type can be constructed directly, because its fields are available from the current scope
|
LL | let crate::Foo(x) = crate::my_mod::Foo(42);
| ~~~~~~~~~~~~~~~~~~
```
Fix #133343.
remove couple of clones2025-09-05T13:38:01+00:00Matthias Krügermatthias.krueger@famsik.de2025-09-05T13:38:01+00:00urn:sha1:81042523c6e1ae50682f46ae3da4ede22bfd596eRollup merge of #145597 - petrochenkov:nolateset, r=b-naber2025-08-23T02:00:51+00:00Jacob Prattjacob@jhpratt.dev2025-08-23T02:00:51+00:00urn:sha1:8066e76c7df47fbcb7eca3e348b920a854919f87
resolve: Remove `ScopeSet::Late`
It's better to decouple the late/early stage from scope set, because in https://github.com/rust-lang/rust/pull/144131#discussion_r2283200511 we'll need the stage for `ScopeSet::Module` as well.
See individual commits for the refactoring details.
r? ``@b-naber``
resolve: Remove `ScopeSet::Late`2025-08-22T13:52:16+00:00Vadim Petrochenkovvadim.petrochenkov@gmail.com2025-08-19T08:59:21+00:00urn:sha1:e26b1754cbd90363b7d5307a8cac31a347af9894
The difference between `Late` and `All` only matters when `finalize` is enabled.
So add a `stage` field to `Finalize` and use it instead.
resolve: Remove derive fallback lint id from `ScopeSet::Late`2025-08-22T13:52:16+00:00Vadim Petrochenkovvadim.petrochenkov@gmail.com2025-08-19T08:37:01+00:00urn:sha1:a47c3729b49f3e5ded7e3c05981dbb27fab96b45resolve: Remove `Module` from `ScopeSet::Late`2025-08-22T13:52:16+00:00Vadim Petrochenkovvadim.petrochenkov@gmail.com2025-08-19T08:07:38+00:00urn:sha1:b82b947a5c6ed8a8bdb155b99298e9e79c93238c
It can be passed in a more usual way through `ParentScope`
print raw lifetime idents with `r#`2025-08-22T04:58:37+00:00Deadbeefent3rm4n@gmail.com2025-08-04T09:41:55+00:00urn:sha1:1e5b5ba1e732d557f00a3cd79150990370c7db0aresolve: Introduce `RibKind::Block`2025-08-14T15:50:57+00:00Vadim Petrochenkovvadim.petrochenkov@gmail.com2025-08-07T16:43:15+00:00urn:sha1:68ebbae2e81b5e88681ec7a25d2aa19c0504a6b4
to avoid confusing module items, blocks with items, and blocks without items.
resolve: Improve code reuse in typo candidate collection2025-08-14T06:53:49+00:00Vadim Petrochenkovvadim.petrochenkov@gmail.com2025-08-13T19:01:02+00:00urn:sha1:9b797b9f7ac12a8ad6a2a5097b69e0216958709eSwitch to a bitflags `MacroKinds` to support macros with more than one kind2025-08-12T16:24:45+00:00Josh Triplettjosh@joshtriplett.org2025-08-08T02:21:16+00:00urn:sha1:0b855bcdc9b0fafa5a4a4330e10655105daf27cb
Review everything that uses `MacroKind`, and switch anything that could
refer to more than one kind to use `MacroKinds`.
Add a new `SyntaxExtensionKind::MacroRules` for `macro_rules!` macros,
using the concrete `MacroRulesMacroExpander` type, and have it track
which kinds it can handle. Eliminate the separate optional `attr_ext`,
now that a `SyntaxExtension` can handle multiple macro kinds.
This also avoids the need to downcast when calling methods on
`MacroRulesMacroExpander`, such as `get_unused_rule`.
Integrate macro kind checking into name resolution's
`sub_namespace_match`, so that we only find a macro if it's the right
type, and eliminate the special-case hack for attributes.