Skip to content

Commit 7271c1a

Browse files
committed
announce feb lang team design meetings
1 parent b2d7cdf commit 7271c1a

File tree

1 file changed

+32
-0
lines changed

1 file changed

+32
-0
lines changed
Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
layout: post
3+
title: "February Lang Team Design Meetings"
4+
author: Niko Matsakis
5+
description: "Lang Team Design Meetings scheduled for February"
6+
team: the language team <https://www.rust-lang.org/governance/teams/lang>
7+
---
8+
9+
We've scheduled our **language team design meetings** for February. The current plans are as follows:
10+
11+
* February 3rd -- we will do an overview of **specialization**. We'll cover details from the RFC but in particular talk about the [as-yet-unimplemented plans to make it sound](http://aturon.github.io/tech/2018/04/05/sound-specialization/).
12+
* February 10th -- we will cover interactions between the `&T` type and LLVM's dereferenceable attribute, such as [rust-lang/rust#55005](https://github.com/rust-lang/rust/issues/55005) and [problems modeling MMIO](https://github.com/japaric/volatile-register/issues/10).
13+
* February 17th -- no meeting, it is President's Day in the US and many of us are absent
14+
* February 24th -- we will summarize discussions from [the ffi-unwind project group] about whether we should permit foreign exceptions to propagate across the "C" ABI boundary, or establish a separate ABI (e.g., "C unwind") for such cases.
15+
16+
[the ffi-unwind project group]: https://github.com/rust-lang/project-ffi-unwind
17+
18+
## About the language team design meetings
19+
20+
The idea of the design meeting is that it's a time for us to have
21+
in-depth discussions on some particular topic. This might be a burning
22+
problem that we've discovered, an update on some existing design work,
23+
or a forward looking proposal.
24+
25+
The meetings are open for anyone to listen in and attend. They are
26+
typically also recorded and posted online, along with minutes, after
27+
the fact. They generally take place on Mondays at "noon Boston time"
28+
-- but for the precise scheduling you should check the [lang team
29+
calendar]. Scheduled meetings are subject to change and
30+
cancelation. In that case, the calendar events will be updated.
31+
32+
[lang team calendar]: https://github.com/rust-lang/lang-team/#meeting-calendar

0 commit comments

Comments
 (0)