The opsem team is the successor of the unsafe-code-guidelines working group and responsible for
answering many of the difficult questions about the semantics of unsafe Rust. It is also a subteam
of the lang team. For more information about the team, see the RFC in which it
was created. For an up-to-date list of members, see the governance section of the
website.
This repo is used primarily for procedural items like meeting proposals. For technical discussions
around unsafe code, see the unsafe code guidelines repo instead.
opsem-team
Home of the operational semantics team.
The opsem team is the successor of the unsafe-code-guidelines working group and responsible for answering many of the difficult questions about the semantics of unsafe Rust. It is also a subteam of the lang team. For more information about the team, see the RFC in which it was created. For an up-to-date list of members, see the governance section of the website.
This repo is used primarily for procedural items like meeting proposals. For technical discussions around unsafe code, see the unsafe code guidelines repo instead.
Chat
Outside of the UCG repo, much of the team’s discussion happens in the
#t-opsemstream on Zulip.Meetings
The team holds weekly meetings. For details around scheduling and format and the calendar of future meetings, see the dedicated page.
FCPs
If you want to get an idea of which decisions have already been made, here is a list of FCPs.
Code of Conduct and licensing
All interactions on this repository (whether on issues, PRs, or elsewhere) are governed by the Rust Code of Conduct.
Further, all content on this repository is subject to the standard Rust licensing.