Skip to content

Month 4-Unsafe Rust, FFI, and Macros

Goal: by the end of week 16 you can (a) write an unsafe fn whose safety contract is documented well enough to survive a security review, (b) bind to a non-trivial C library and also expose a Rust library to C consumers, (c) write a macro_rules! that respects hygiene and can be re-imported, and (d) ship a procedural macro that derives a non-trivial trait with custom attributes and useful diagnostics.


Weeks

Comments