You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Woooo--the Unsafe Code Guidelines working group is *officially* rebooted! See the [zulip log](https://rust-lang.zulipchat.com/#narrow/stream/136281-wg-unsafe-code-guidelines/topic/meeting.202018-08-30) for all of the gory details.
4
+
5
+
The meetings are intended to be mostly administrative and *not* focus on technical details, but rather evaluate the WG progress and see where we should focus our efforts.
6
+
7
+
## Takeaways
8
+
* We'll be moving meetings to (roughly) every 2 weeks on Thursdays at 1515 UTC (ping @nikomatsakis if you want an official calendar invite)
9
+
* Our very first **active discussion** will be...Data structure representation layout!
10
+
* The "validity invariant" discussion will be left as future work
11
+
* Let's make a [glossary][glossary] to get everyone on the same terminology page
* Define "invalid ranges" for values we require currently and those we want to guarantee
19
+
* Which Rust types have defined binary representations
20
+
* If/when can you reinterpret a type?
21
+
22
+
Active topics are divided into [issues][active]. Keeping the discussions centralized in these issues should help us keep the discussion open and asynchronous. We're happy to reevaluate this approach--reach out to @avadacatavra or @nikomatsakis in [Zulip][zulip] if you have comments/concerns.
23
+
24
+
## Goals
25
+
26
+
* Reach a consensus on some representations and work towards a writeup on them (hopefully)
27
+
* Identify any areas where there's a less obvious answer and what the options are
0 commit comments