RFC: In Order to Form a More Perfect `union`
summary
Proposal shows the concrete outcome: RFC1444 added union after 16 months, three RFCs and half a dozen syntaxes. The RFC documents choices, interactions with borrow/drop/traits, and corner cases rather than vague examples. Implementation lands behind a feature flag and is implemented in nightly (tracking issue active, Petrochenkov credited). A minimal KVM binding using the new union type compiles and runs a smoke test — the KVM test prints "4" showing the approach actually works.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:35Virtual Machines
- 2:15Linux Kernel Virtual Machine Api
- 9:16Rfc 724 for Unsafe Enum
- 9:56Keywords
- 13:26Contextual Keyword
- 14:18Language Interactions
- 14:45Visibility Annotations
- 17:03How Do You Make an Rfc Move Forward
- 19:09Implement the Kvm Api
- 23:27The State of the Rfc Process
- 25:15Pre Rfc Discussion
related talks
59mPolymorphism with Unions
24mRFC: Secret types in Rust
21mUsing Ghost Ownership to Verify Union-Find and Persistent Arrays in Rust
17mExploring a real life RCU use case for Rust
01h 11mDuck-Tape Chronicles - Rust C++ Interop
35mRust for Linux Office Hours
20mRust language evolutions for better kernel developer experience
25mType System Tips for the Real World