user0/rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add link to RFC2033 in walkthrough

Browse source
This commit is contained in:
Redddy 2026-01-20 21:53:25 +09:00 • committed by GitHub
parent f28c32abc6
commit 156cb44ab0
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 5 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

8
src/doc/rustc-dev-guide/src/walkthrough.md
View file

@ -166,9 +166,11 @@ is clear, but the design space is too large to settle on a detailed specificatio
Instead of providing a final design, an eRFC outlines a high-level strategy to authorize
a period of active experimentation. This allows the team to implement the feature behind
a feature gate and gather practical data, which then informs a subsequent formal RFC for stabilization.
While this process was used for major features like coroutines, the explicit "eRFC" label
is rarely used today. The project now generally prefers approving a standard RFC for an initial
version and iterating on it through the nightly channel before final stabilization.
While this process was used for major features like coroutines ([see RFC2033][rfc2033]),
the explicit "eRFC" label is rarely used today. The project now generally prefers approving a standard
RFC for an initial version and iterating on it through the nightly channel before final stabilization.
[rfc2033]: https://github.com/rust-lang/rfcs/pull/2033#issuecomment-309057591
<a id="impl"></a>