rustc-dev-guide
rustc-dev-guide copied to clipboard
rust-lang
A guide to how rustc works and how to contribute to it.
r? @alice-i-cecile
This PR improve the documentation of MIR queries and passes. Below is the summary of changes: - delete `mir_validated` - add `mir_promoted` and `mir_drops_elaborated_and_const_checked` - replace the `NoLandingPads` pass example...
Previously, "Building and debugging `rustc`" linked to the getting started page, which isn't correct. If people want that page, it already appears in the sidebar, and is the next sequential...
Correct. The `[patch]` tables are gone. BTW, I was noticing that there seems to be a lot of detailed information about git in this "introduction" chapter. Almost nobody needs to...
Also, keep it trimmed... if a formal policy is adopted, this text can be updated to indicate so.
## Procedure Each of these dates should be checked to see if the docs they annotate are up-to-date. Each date should be updated (in the Markdown file where it appears)...
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "github-actions[bot] avatar"){kind=avatar}
Took me a while to find out [what an eRFC is](https://github.com/rust-lang/rfcs/pull/2033#issuecomment-309057591), I believe such information should also be in the dev-guide, but it isn’t AFAICT.
As @Zoxc's work to [parallelize rustc] starts to land, we need to start documenting it! Some example topics: - Copy some of the text from the internals thread as to...
https://rustc-dev-guide.rust-lang.org/building/how-to-build-and-run.html?highlight=platform#building-targets-for-cross-compilation ``` thread 'main' panicked at 'Target "wasm32-wasi" does not have a "wasi-root" key', compile.rs:268:17 ``` I've also tried `x86_64-apple-darwin` and that fails because the gcc `-arch` flag doesn't exist...
