Skip to content

Commit 5b871d7

Browse files
committed
lang team february update
1 parent 4132c37 commit 5b871d7

File tree

1 file changed

+45
-0
lines changed

1 file changed

+45
-0
lines changed
Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
---
2+
layout: post
3+
title: "Lang team February Update"
4+
author: Niko Matsakis
5+
description: ""
6+
team: the lang team <https://lang-team.rust-lang.org/>
7+
---
8+
9+
Today the lang team held its first planning meeting ([minutes]). From now on, we're going to hold these meetings on the first Wednesday of every month.
10+
11+
The planning meeting is used for:
12+
13+
* Checking in on the status of our active projects
14+
* Planning the design meetings for the remainder of the month
15+
16+
After each meeting, we plan to post an update (like this one!) with notes and meeting announcements.
17+
18+
[minutes]: https://github.com/rust-lang/lang-team/blob/master/design-meeting-minutes/2021-02-03-Planning-Meeting.md
19+
20+
## Update from active projects
21+
22+
Did you know that you can see the lang team's active projects on our [project board](https://github.com/rust-lang/lang-team/projects/2)? We're still experimenting and evolving the setup, but the goal is that it should give you a quick overview of what kinds of things the lang team is focused on, and what stage they are in their development. Our minutes contain a [writeup for each active project](https://github.com/rust-lang/lang-team/blob/master/design-meeting-minutes/2021-02-03-Planning-Meeting.md#project-updates-and-discussion), but let me call out a few highlights here:
23+
24+
* async foundations:
25+
* continued progress on polish, new traits
26+
* making plans to stabilize async functions in traits
27+
* working on a [vision document](https://hackmd.io/p6cmRZ9ZRQ-F1tlhGaN9rg) that lays out a multi-year vision for how async I/O should look/feel in Rust
28+
* const generics:
29+
* min const generics is stable in nightly, will be coming to a stable release soon
30+
* rfc 2229 ("minimal closure capture"):
31+
* continued progress on the implementation, things are going well
32+
* we will likely add a `capture!` macro to use for migration; it would force the capture of a particular local variable (and not some subpath of it)
33+
* inline assembly
34+
* we would like to consider stabiliing inline assembly for certain architectures (but not all)
35+
36+
## Upcoming design meetings
37+
38+
We planned three design meetings for February. Our meetings are typically open for anyone to observe, although we have one closed meeting this week. They are also typically recorded and posted to YouTube. Ping nikomatsakis or joshtriplett for info about attending.
39+
40+
* Feb 10 \[CLOSED\]: [Growing the team](https://github.com/rust-lang/lang-team/issues/81). The plan is to talk about our plans to grow the team and recruit new members. **Closed because we expect some frank talk about who might be a good candidate.**
41+
* Feb 17: [Improving trust in the Rust compiler](https://github.com/rust-lang/lang-team/issues/79), discussing the Ferrocene proposal and the semantics of MIR.
42+
* Feb 24: [2021 idiom lint overview](https://github.com/rust-lang/lang-team/issues/83), discussing the various 2018 idiom lints and whether they ought to be included in 2021.
43+
44+
45+

0 commit comments

Comments
 (0)