Skip to content

added meeting notes #18

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 31, 2018
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 32 additions & 0 deletions meeting-notes/20180308.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
# Meeting 0: 30 Aug 2018

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.

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.

## Takeaways
* We'll be moving meetings to (roughly) every 2 weeks on Thursdays at 1515 UTC (ping @nikomatsakis if you want an official calendar invite)
* Our very first **active discussion** will be...Data structure representation layout!
* The "validity invariant" discussion will be left as future work
* Let's make a [glossary] [glossary] to get everyone on the same terminology page

[glossary]: https://github.com/rust-rfcs/unsafe-code-guidelines/blob/master/reference/src/introduction.md

## What's next

Go discuss!
* Define "invalid ranges" for values we require currently and those we want to guarantee
* Which Rust types have defined binary representations
* If/when can you reinterpret a type?

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.

## Goals

* Reach a consensus on some representations and work towards a writeup on them (hopefully)
* Identify any areas where there's a less obvious answer and what the options are

[active]: https://github.com/rust-rfcs/unsafe-code-guidelines/issues?q=is%3Aopen+is%3Aissue+label%3A%22active+discussion+topic%22
[zulip]: https://rust-lang.zulipchat.com/#narrow/stream/136281-wg-unsafe-code-guidelines

See you in the GH discussion!
11 changes: 11 additions & 0 deletions reference/src/introduction.md
Original file line number Diff line number Diff line change
@@ -1 +1,12 @@
# Introduction


## Terms

(TODO: definitions)

* *niche*
* *layout*
* *tag*

## Unsafe abstraction