# \`cfg(extern = "rand")\`

**URL:** <https://internals.rust-lang.org/t/cfg-extern-rand/24470>\
**Category:** language design\
**Created:** [July 14, 2026, 10:08pm UTC](https://internals.rust-lang.org/t/cfg-extern-rand/24470 "2026-07-14T22:08:35Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![epage](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/epage/32/3171_2.png) [@epage](https://internals.rust-lang.org/u/epage)\
**Post date:** [July 15, 2026, 11:30am UTC](https://internals.rust-lang.org/t/cfg-extern-rand/24470/6 "2026-07-15T11:30:56Z")

</div>

This is getting into

> They are also extending some low level features further into Cargo and there would need to be some deliberation of what kind of line should be drawn for that.

We've previously rejected a `[cfg]` table. Cargo focuses on abstractions of rustc features, for example we have features for defining one kind of cfg and we want globals / package parameters as another kind of cfg ([Pre-RFC: Mutually-excusive, global features](https://internals.rust-lang.org/t/pre-rfc-mutually-excusive-global-features/19618)).

---

_[View the full topic](https://internals.rust-lang.org/t/cfg-extern-rand/24470)._