Moving `cfg(accessible)` forward by narrowing down its scope(part of RFC2523)

Theoretically, it could optimistically resolve to the external crate name, and register a requirement for that name to not become ambiguous later. We're effectively saying that the path must resolve to an external crate name, and it's an error if it doesn't.

I think this should work similarly to macro names ambiguous with macro expanded macro names.

1 Like