Skip to content

One glossary should be enough #19

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.

Sign up for GitHub

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
Sep 10, 2018
+1 −1
Merged

One glossary should be enough #19

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion meeting-notes/20180308.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ The meetings are intended to be mostly administrative and *not* focus on technic
* 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
* 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

Expand Down