I read the thread, and couldn't disagree more.

> If Rust isn’t memory safe (because unsafe), and Zig isn’t (because uaf), then Fil-C isn't (because zunsafe_call/zunsafe_fast_call).

Rust isn’t memory safe (because unsafe) isn't an argument anyone makes, it's that Rust that uses unsafe isn't memory safe!

It's called `unsafe` for a reason dude, not even the Rust people think it's safe.

> Rust isn’t memory safe (because unsafe) isn't an argument anyone makes

This is an argument that Fil-C makes, by choosing a very specific definition of memory safety. It’s even stated explicitly in that tweet linked.