The Second First Rustc Reading Club

The Rustc Reading Club is coming again on December 2, 2021 at 12PM EST. Your timezone here.

The response to the first scheduled Rustc Reading Club on November 4, 2021 has made it clear that we need to do two things. First, we need to reschedule with a smaller more manageable group. Second, the popularity of this experiment means that we need a way to scale to enable more people to participate. So if you are tempted to lead a rust related code reading club, we want to hear from you! You can reach out in the Zulip stream, or add an “Organizer Request” issue in the Github repo.

To be considered for the smaller cohort, complete this signup form.

Rustc Reading Club Signup Form

How does this thing work?

Rustc Reading Club is a group of 10 to 15 people that will work through a series of exercises to become familiar with the selected module of the compiler. Niko Matsakis has selected the name resolver crate as the first topic for our Rustc Reading Club pilot. He will present and guide us through exercises that will be completed individually and then shared with the group.

Each session will last 90 minutes and completing the exercises for a single crate/module will require multiple sessions. The number of sessions devoted to a single module will depend on the size of the module.

We will learn together through offering our individual impressions of the code and listening to the impressions of our fellow group members.

As a final note, these sessions will not be recorded.

Final final note, because this is an experiment any of the above could change as we keep the things that work and adjust or replace the things that don’t.

What do I need to know to attend?

You should be reasonably familiar with Rust syntax. You don’t have to be an expert on every corner of the language (although learning about the compiler can definitely help to make you an expert).

Familiarity with compiler concepts is helpful but not required. Experience with rustc is of course also helpful but not required. Feel free to ask questions if people are using compiler or rustc jargon that you don’t understand!

That said, we do want to say something up front: if you’re not familiar with rustc already, you will definitely have a “jumping into the deep end of the pool” feeling. That’s ok — and guess what, even the people who are familiar with rustc will feel that from time to time. Stick it out, ask questions, and you should learn a lot.

Got a compiler topic proposal?

If you have a suggestion for a rustc module that you would like to learn more about, add a “Topic Proposal” issue in the Github repo.

“If it’s not written down, it doesn’t exist.” — Philippe Krutchen