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

Fix MCP links

This commit is contained in:
Jakub Beránek 2025-03-14 15:18:58 +01:00
parent 9975f62f2b
commit dad3718db8
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/contributing.md
View File

@ -81,7 +81,7 @@ smaller user-facing changes.
into a PR that ends up not getting merged!** [See this document][mcpinfo] for into a PR that ends up not getting merged!** [See this document][mcpinfo] for
more info on MCPs. more info on MCPs.
[mcpinfo]: https://forge.rust-lang.org/compiler/mcp.html [mcpinfo]: https://forge.rust-lang.org/compiler/proposals-and-stabilization.html#how-do-i-submit-an-mcp
[zulip]: https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler [zulip]: https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler
### Performance ### Performance

2
src/implementing_new_features.md
View File

@ -44,7 +44,7 @@ like this; for example, the compiler team recommends
filing a Major Change Proposal ([MCP][mcp]) as a lightweight way to filing a Major Change Proposal ([MCP][mcp]) as a lightweight way to
garner support and feedback without requiring full consensus. garner support and feedback without requiring full consensus.
[mcp]: https://forge.rust-lang.org/compiler/mcp.html#public-facing-changes-require-rfcbot-fcp [mcp]: https://forge.rust-lang.org/compiler/proposals-and-stabilization.html#how-do-i-submit-an-mcp
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