Skip to content

Commit e3c263a

Browse files
authored
Apply suggestions from code review
Co-authored-by: Pete LeVasseur <plevasseur@gmail.com>
1 parent d781f91 commit e3c263a

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

  • subcommittee/liaison/meetings/2026-05-26-opsem-expert-session

subcommittee/liaison/meetings/2026-05-26-opsem-expert-session/minutes.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ Mini Rust talk given at last year’s RustWeek 2025
7272

7373
* [MiniRust: A core language for specifying Rust \- Ralf Jung](https://www.youtube.com/watch?v=yoeuW_dSe0o)
7474

75-
Some Operational Semantics Concerns are outside of Rust
75+
Making progress on some OpSem questions requires stakeholders outside the Rust project.
7676

7777
* E.g. make sure that LLVM does the right thing
7878
* Mapping same memory into multiple address spaces kicks out a potentially large number of optimizations that LLVM does
@@ -81,7 +81,7 @@ Some Operational Semantics Concerns are outside of Rust
8181

8282
* Written in Rust
8383
* Going to safety-certify
84-
* Working to understand the Rust reference and the standard library docs to make sure know how to rest a safety argument
84+
* Working to understand the Rust reference and the standard library docs to make sure we know how to rest a safety argument on normative documentation
8585

8686
Shared memory, for example, seems challenging to describe accurately via the Rust Abstract Machine
8787

0 commit comments

Comments
 (0)