2019.01.04
We discussed the upcoming Rust All Hands. We have a HackMd document that lists a bunch of ideas for what to talk about, but mostly we talked about how to structure the meeting itself.
We summarized how the All Hands was structured last year: basically meetings focused around particular topics, with the team (and others) mostly in a kind of semi-circle or around a whiteboard.
One of the ideas we had for this year is that we could have some sessions that are just focused on explaining how a particular area of the code works, which could help people unfamiliar with an area get up to speed.
In general, we decided that each of our slots should begin with some exposition of “how things work now”, and then segway into “here are problems to resolve”. We will try to take good notes on these expositions as well.
We discussed how it might also be useful to talk about some of the tools that are “adjacent” to the compiler, e.g., rustdoc or RLS.
We discussed some possibler areas for discussion:
- the rustc-dev-guide
- related work, like RLS, rustdoc, or cranelift
- mentoring?
- maybe, but we have to figure out specifically what
- salsa, polonius, chalk, etc
- diagnostics
On the topic of IDEs, it would be useful to hear from Matklad about rust-analyzer.
We also thought a bit about some more “radical” ideas that might be worth making a bit more concrete: