A guide to how rustc works and how to contribute to it.
Go to file
Mark Mansi eec934f762 fix remaining links 2018-06-02 17:20:47 -04:00
ci update to mdbook 0.1.7 2018-05-08 12:44:02 -05:00
src fix remaining links 2018-06-02 17:20:47 -04:00
.editorconfig Added EditorConfig file for `src`. 2018-03-26 20:28:00 -05:00
.gitignore add outline and chapters 2018-01-16 17:35:19 -05:00
.travis.yml Add mdbook test to Travis 2018-04-06 14:18:08 -05:00
CODE_OF_CONDUCT.md Changed all instances of `e.g.,` to `e.g.`, and similar. 2018-02-04 21:46:26 -06:00
LICENSE-APACHE add code-of-conduct, licensing material, and a README 2018-01-16 16:36:21 -05:00
LICENSE-MIT add code-of-conduct, licensing material, and a README 2018-01-16 16:36:21 -05:00
README.md Consolidate and fix code blocks 2018-04-06 14:18:08 -05:00
book.toml Add mdbook search. 2018-03-22 13:55:55 -05:00

README.md

This is a collaborate effort to build a guide that explains how rustc works. The aim of the guide is to help new contributors get oriented to rustc, as well as to help more experienced folks in figuring out some new part of the compiler that they haven't worked on before.

You can read the latest version of the guide here.

The guide can be useful today, but it has a lot of work still go. Once it gets more complete, the plan is probably to move it into the main Rust repository.

Contributing to the guide

If you'd like to help finish the guide, we'd love to have you! The main tracking issue for the guide can be found here. From there, you can find a list of all the planned chapters and subsections -- if you think something is missing, please open an issue about it! Otherwise, find a chapter that sounds interesting to you and then go to its associated issue. There should be a list of things to do.

In general, if you don't know how the compiler works, that is not a problem! In that case, what we will do is to schedule a bit of time for you to talk with someone who does know the code, or who wants to pair with you and figure it out. Then you can work on writing up what you learned.

To help prevent accidentally introducing broken links, we use the mdbook-linkcheck. If installed on your machine mdbook will automatically invoke this link checker, otherwise it will emit a warning saying it couldn't be found.

> cargo install mdbook-linkcheck

You will need mdbook version >= 0.1. linkcheck will be run automatically when you run mdbook build.