I didn’t understand this. He said the bickering between C and rust devs reminds him of the vim/emacs debate.
I didn’t understand this. He said the bickering between C and rust devs reminds him of the vim/emacs debate.
Nice writeup. I was surprised by the lack of performance of the Bevy solution, especially the fact that it didn’t scale. In fact I was a bit saddened Bevy has no existing way it doing fast whole-objects collision detection.
I love you. That’s exactly what I was looking for. Long live Hevilix !
I’m just there for a cheap joke. Hope it didn’t hurt ! (BTW I have already been given the boot by HR. Can’t correctly express my feeling about them.)
Plot twist: 95% of the engineering team was fired once the code was “done”. Including the poor schmuck who authored this.
Regardless of the very subject of the post, linear types and do.. final
constructs would be a welcomed addition.
Warning: in the first case “value” is actually a shared reference, not a value.
You could argue that C++'s new is Rust’s Box::new, and delete is replaced by RAII. Same concepts but way better ergonomy.
I find it’s a mix between ML languages and C++, and knowing one of them would help yes. If you’re tired if chasing a wild pointer because of a subtle use-after-free in a multithreaded monster under gdb, you’ll love #rust.
I’ll start.
0.0.0.1: Sophie
Your turn.
That’s a hell of a comment !
That thing is rock solid, it’s nearly magical.
Type-B USB ? Eww …