References - Safety in an Unsafe World - RustConf 2024

references.md

References

From Safety in an Unsafe World at RustConf 2024

Video | Slides

Contact

joshlf.com | hello@joshlf.com | joshlf@google.com | @joshlf_ | reddit.com/u/joshlf_

Citations

• [1] Prior art (crates):
  • zerocopy
  • session_types
  • indexing
  • bytemuck
  • ghost-cell
  • nalgebra
  • mundane
• [2] Prior art (writing):
  • Rust
    • References are like jumps
    • Some notes on Rust, mutable aliasing and formal verification
    • Compiler-driven development in Rust
    • The Typestate Pattern in Rust
  • Non-Rust
    • Parse, don't validate
    • Type Safety Back and Forth
    • Ghosts of Departed Proofs (Functional Pearl)
• [3] RFC 4614 Section 2
• [4] RFC 4614 Section 3
• [5] Lock ordering crates
  • lock_ordering on crates.io
  • lock_order in Fuchsia (docs | source)
• [6] [netstack3] Default to 4 threads
• [7]
  • Parse, don't validate
  • Type Safety Back and Forth
• [8] Simplicity is Complicated, Slide 18 - Rob Pike

Further reading

• Move fast and don't break things: High performance networking in Rust - my talk from Rust Belt Rust 2018
• Netstack3's net-types crate
• Zerocopy's Ptr smart pointer abstraction
  • We're considering publishing this abstraction for others to use. If this sounds interesting to you, please let us know!
• interprocess-traits crate
• Functional Core, Imperative Shell
  • Netstack3 uses an architecture inspired by this concept, although since it's in Rust, the core is able to perform mutation. This allows Netstack3's "core" (~90% of the codebase) to be completely platform-agnostic. Only 10% of Netstack3 knows it's running on Fuchsia.
• Come hang out on the zerocopy Discord!

thanks for the slideshow, and this
my grok went up a few notches