A guide to how rustc works and how to contribute to it.
Go to file
Niko Matsakis 141528264b move over the `ty` README 2018-01-19 06:51:52 -05:00
ci Created a couple basic CI scripts 2018-01-17 12:30:45 +08:00
src move over the `ty` README 2018-01-19 06:51:52 -05:00
.gitignore add outline and chapters 2018-01-16 17:35:19 -05:00
.travis.yml Created a couple basic CI scripts 2018-01-17 12:30:45 +08:00
CODE_OF_CONDUCT.md add code-of-conduct, licensing material, and a README 2018-01-16 16:36:21 -05: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 add link to gh-pages 2018-01-17 09:53:45 -05:00
book.toml add outline and chapters 2018-01-16 17:35:19 -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.