Skip to content

Document experimental RFC process in walkthrough #2734

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tshepang merged 4 commits into from
Jan 23, 2026
Merged

Document experimental RFC process in walkthrough #2734

Changes from 3 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
77366fd
Add link to internals.rust-lang.org in walkthrough
reddevilmidzy Jan 20, 2026
e2056c8
Document experimental RFC process in walkthrough
reddevilmidzy Jan 20, 2026
fecdf2a
Add link to RFC2033 in walkthrough
reddevilmidzy Jan 20, 2026
22282e2
Fix typo
reddevilmidzy Jan 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 14 additions & 1 deletion src/walkthrough.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,7 +97,7 @@ If that sounds like a lot of work, it's because it is.
But no fear!
Even if you're not a compiler hacker, you can get great feedback by doing a _pre-RFC_.
This is an _informal_ discussion of the idea.
The best place to do this is internals.rust-lang.org.
The best place to do this is [internals.rust-lang.org](https://internals.rust-lang.org).
Your post doesn't have to follow any particular structure.
It doesn't even need to be a cohesive idea.
Generally, you will get tons of feedback that you can integrate back to produce a good RFC.
Expand Down Expand Up @@ -159,6 +159,19 @@ Here is the tracking issue on for our [`?` macro feature][tracking].

[tracking]: https://github.com/rust-lang/rust/issues/48075

## Experimental RFC (eRFC)

An eRFC is a variant of the RFC process used for complex features wherethe high-level need
is clear, but the design space is too large to settle on a detailed specification upfront.
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 ([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>

## Implementation
Expand Down
Loading