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

**URL:** <https://internals.rust-lang.org/t/moving-cfg-accessible-forward-by-narrowing-down-its-scope-part-of-rfc2523/22373>\
**Category:** Uncategorized\
**Created:** [February 11, 2025, 1:28am UTC](https://internals.rust-lang.org/t/moving-cfg-accessible-forward-by-narrowing-down-its-scope-part-of-rfc2523/22373 "2025-02-11T01:28:07Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![CAD97](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/cad97/32/3460_2.png) [@CAD97](https://internals.rust-lang.org/u/CAD97)\
**Post date:** [February 17, 2025, 8:27pm UTC](https://internals.rust-lang.org/t/moving-cfg-accessible-forward-by-narrowing-down-its-scope-part-of-rfc2523/22373/17 "2025-02-17T20:27:33Z")

</div>

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.

---

_[View the full topic](https://internals.rust-lang.org/t/moving-cfg-accessible-forward-by-narrowing-down-its-scope-part-of-rfc2523/22373)._