|
| 1 | +--- |
| 2 | +layout: post |
| 3 | +title: "Lang Team Design Meetings" |
| 4 | +author: Niko Matsakis |
| 5 | +description: "Lang Team Design Meetings" |
| 6 | +team: the language team <https://www.rust-lang.org/governance/teams/lang> |
| 7 | +--- |
| 8 | + |
| 9 | +Hi all! I wanted to give a quick update about the lang team. We're |
| 10 | +starting something new this year: a regular **design meeting**. The |
| 11 | +idea of the design meeting is that it's a time for us to have in-depth |
| 12 | +discussions on some particular topic. This might be a burning problem |
| 13 | +that we've discovered, an update on some existing design work, or a |
| 14 | +forward looking proposal. |
| 15 | + |
| 16 | +The meetings will be scheduled in advance. Ideally, each meeting |
| 17 | +should also have a blog post before-hand giving background material, |
| 18 | +although that may be difficult to achieve in practice. Similarly, |
| 19 | +after each meeting, we'll typically post minutes and a recording, and |
| 20 | +ideally try to write up a summary blog post with major |
| 21 | +points. (Sometimes recordings are hard to achieve, either for |
| 22 | +technical reasons or because we wanted the ability to discuss more |
| 23 | +sensitive topics.) |
| 24 | + |
| 25 | +The meetings are open for anyone to listen in and attend. They |
| 26 | +generally take place on Mondays at "noon Boston time" -- but for the |
| 27 | +precise scheduling you should check the [lang team calendar]. We'll |
| 28 | +try to keep the calendar up to date with the topic to be discussed in |
| 29 | +each meeting, as well. Meetings might not happen every week, if we |
| 30 | +don't have a topic in mind. |
| 31 | + |
| 32 | +[lang team calendar]: https://github.com/rust-lang/lang-team/#meeting-calendar |
| 33 | + |
| 34 | +## First design meeting |
| 35 | + |
| 36 | +Our first design meeting was actually last Monday! We discussed the |
| 37 | +soundness hole that was found some time ago in `Pin`. You can read |
| 38 | +the [minutes] from our discussion and a [recording] is also |
| 39 | +available. You might also find it easier to read the [comments in the |
| 40 | +internals thread][comments]. The good news is that we seem to be |
| 41 | +centralizing on a [solution based on negative impls][neg]. |
| 42 | + |
| 43 | +[minutes]: https://github.com/rust-lang/lang-team/blob/master/design-meeting-minutes/2020-01-06-Pin-unsoundness.md |
| 44 | +[recording]: https://youtu.be/MX_GRNLhlY8 |
| 45 | +[comments]: https://internals.rust-lang.org/t/unsoundness-in-pin/11311/112?u=nikomatsakis |
| 46 | +[neg]: https://internals.rust-lang.org/t/explicit-negative-impls-to-fix-pin-soundness-hole/11587 |
| 47 | + |
| 48 | +## Next design meeting |
| 49 | + |
| 50 | +The next design meeting will take place this coming Monday. The topic |
| 51 | +will be how to fix [rust-lang/rust#57893], which is a soundness bug |
| 52 | +related to `dyn` types. There is a [prepared writeup describing the |
| 53 | +problem and a possible solution][gist] to guide the meeting. It is |
| 54 | +maybe worth noting that one of the proposed solutions involved a Rust |
| 55 | +2021 edition as well (although there are smaller, more targeted fixes |
| 56 | +that do not require a new edition). |
| 57 | + |
| 58 | +[rust-lang/rust#57893]: https://github.com/rust-lang/rust/issues/57893 |
| 59 | +[gist]: https://gist.github.com/0cf84ac05ce7751b5759cbf335c4d327 |
| 60 | + |
| 61 | +## Design meetings after that |
| 62 | + |
| 63 | +The next two weeks are likely to not have design meetings: |
| 64 | + |
| 65 | +* January 20th is Martin Luther King, Jr. day in the US. |
| 66 | +* January 27th is the Mozilla All Hands. |
| 67 | + |
| 68 | +As a result, in both cases, many of the lang team members will be |
| 69 | +unable to attend. |
0 commit comments