mirror
/
rustc-dev-guide
mirror of https://github.com/rust-lang/rustc-dev-guide.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Link from "implementing to new features" to mcp.md (#1465)

This commit is contained in:
Felix S Klock II 2022-09-15 18:06:59 -04:00 committed by GitHub
parent cf7c209ce2
commit 00db68b612
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/implementing_new_features.md
View File

@ -28,6 +28,12 @@ get by with only an r+. For example, it is OK to add or modify
unstable command-line flags or attributes without an FCP for unstable command-line flags or attributes without an FCP for
compiler development or standard library use, as long as you don't compiler development or standard library use, as long as you don't
expect them to be in wide use in the nightly ecosystem. expect them to be in wide use in the nightly ecosystem.
Some teams have lighter weight processes that they use in scenarios
like this; for example, the compiler team recommends
filing a Major Change Proposal ([MCP][mcp]) as a lightweight way to
garner support and feedback without requiring full consensus.
[mcp]: compiler/mcp.md#public-facing-changes-require-rfcbot-fcp
You don't need to have the implementation fully ready for r+ to propose an FCP, You don't need to have the implementation fully ready for r+ to propose an FCP,
but it is generally a good idea to have at least a proof but it is generally a good idea to have at least a proof