@filpizlo@kssreeram Every type system has a way to say "trust me bro". Rust is no different. You have to use that feature responsibly or suffer the consequences.
We have TSAN and Miri to catch these cases at runtime already, although I wouldn't mind something like Fil-C for unsafe Rust in prod.
Bro I'm so sick of pretending this isn't weird.
The internet spent 20 years creating tutorials, open-source projects, blog posts & answers for free.
AI companies turned all of it into products worth billions.
And now the same people who created that knowledge are being told they're replaceable.
We built the library.
Someone else started charging admission.
@TheGingerBill@icpolicy The only situation where you would want to conditionally call a destructor is if you are passing that responsibility elsewhere, which is handled by RAII as a move.
@ID_AA_Carmack "Manual checkpointing and cooperative multitasking is an option, but it complicates codebases and is fertile ground for bugs."
Not with async Rust! eg https://t.co/MEqeoA2scL.
@vectorware are working on the ecosystem around Rust targeting GPUs. Maybe this could include async?
@willmcp2@matthiasendler Yeah its like the perfect lang for compilers. Systems level performance with nice functional features like ADTs and pattern matching that compilers often use.
@JustDeezGuy@pandam0nial >terms indexed by types = overloaded functions
I think you mean generic functions
Overloads are just a fancier name resolution, not an edge on the lambda cube
@iluvconchshells @lauriewired Every major software project is eventually polyglot. You just can't get very far within the limitations of a single language. The fact that Linux got this and is still 98% C is a miracle.