A new phase for the Rustc Reading Club

doc docs
2 min readFeb 2, 2022

We’ve been experimenting with the flow and content of Rustc Reading Club since October of 2021. Now that it seems we have the flow worked out, and that it is really different from where we started, time to move to the next phase.

We’ve been introduced to new tools and Feb 3rd 2022, we will conduct our first retrospective to get feedback from everyone. Those aren’t the only new elements of RRC. We’re adding a couple of special sessions over the next month to get more insight into both the name resolver module that we’ve been poking at and the tool we’ll use to poke more at this and other modules.

Upcoming RRC schedule:

Feb 3, 2022: Felix Klock leads a Pernosco tutorial, and we complete a RRC retrospective.

Feb 17, 2022: No meeting

March 3, 2022: Vadim Petrochenkov leads a tutorial of the name resolver.

March 17: Niko again leads us into the code of rustc.

The other big change coming to Rustc Reading Club is video recordings. Felix will record his Pernosco tutorial and post it to his YouTube channel. The name resolver tutorial by Petrochenkov will also be recorded. One of the outcomes of the retrospective will be a decision on whether we will record Phase 2 sessions. The driver for this change is largely due to the fact that Niko has begun to open the session with a description of the section of code that we are grappling with in that session. There is value to the community to share these descriptions so it makes sense to record them.

I’m sure many people will be happy with our process into video recording. Be prepared to fast forward! There are 15 min and 10 min silences as participants in RRC consider and read through the code on their own. I think the content presented in the non silent parts will make the inconvenience of that silence worth the trade.

Next week with the results of our retrospective I’ll share another update on what to expect from future RRCs. Niko has taken us far as he tuned the session flow. I’m convinced that including Pernosco and being able to watch the code as it executes from various perspectives is going to help us learn how to understand rustc together and on our own.

--

--

doc docs

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