Yup, along with other closure proposals too.
There is one safety related proposal that I would like to see implemented: Proposal: Owned pointer type hint · Issue #3690 · ziglang/zig · GitHub
If zig had owned pointers with single move semantics, it means that we can guarantee to free resources exactly once (no way to forget free, or double free). This is a lightweight mechanism, not Rust complex lifetime semantics.
2 Likes
Thanks for digging that functions as expressions
issue up - I couldn’t remember what it was called. BTW, I can see safety features like that getting more widely adopted as the compiler gets more developed. For tooling, that’s a really interesting idea.
1 Like
FWIW, the native x86_64 backend is already very usable!