diff options
| author | Felix S Klock II <pnkfelix@pnkfx.org> | 2022-09-15 18:06:59 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-09-16 07:06:59 +0900 |
| commit | 5aeea2dd7d06201a8783fc9c42df7ef581370b62 (patch) | |
| tree | f0afc8aab48df2822b4ac45740fcecb0a463a304 /src/doc/rustc-dev-guide | |
| parent | 9591f71fb654d891a288880193ac9292d065e585 (diff) | |
Link from "implementing to new features" to mcp.md (#1465)
Diffstat (limited to 'src/doc/rustc-dev-guide')
| -rw-r--r-- | src/doc/rustc-dev-guide/src/implementing_new_features.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/src/doc/rustc-dev-guide/src/implementing_new_features.md b/src/doc/rustc-dev-guide/src/implementing_new_features.md index 36799a2d3b6..9147c1b4132 100644 --- a/src/doc/rustc-dev-guide/src/implementing_new_features.md +++ b/src/doc/rustc-dev-guide/src/implementing_new_features.md @@ -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 compiler development or standard library use, as long as you don't 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, but it is generally a good idea to have at least a proof |