Brendan Zabarauskas on Twitter: "@jonmsterling @dbp__ Yeah it was a bummer of a response, but I think that Rust is doing a good job at this, even if it takes time and the initial explorations annoy some people, initially. I'm very glad for the RustBelt work, for the API improvements in std::mem, and for the stuff miri has uncovered." / Twitter

You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more

I think you’ll find that most OCaml code that does anything performant has either unsafe (Obj.magic) or C underlying it somewhere. E.g., just at a quick glance, looks like Mirage libraries that claim to be pure OCaml use bigarray, which is C. Rust is trying to move that code in.

1

3

You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more

Daniel Patterson

@dbp__

Mar 31

Sorry, I didn’t see the ticket, but some people do care about the semantics. Theres a (maybe defunct) project “unsafe code guidelines” trying to give extensional behavior to safe rust types. Unsafe rust _can_ be given precise semantics, and different ones than C! Seems useful.

1

2

You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more

Replying to

and

Yeah it was a bummer of a response, but I think that Rust is doing a good job at this, even if it takes time and the initial explorations annoy some people, initially. I'm very glad for the RustBelt work, for the API improvements in std::mem, and for the stuff miri has uncovered.

1:51 PM · Mar 31, 2022Twitter Web App

2

Likes

Conversation