Trying to write C/C++ after writing Rust feels ridiculous. Why should I have to keep track of things that the compiler can do for me, especially when the consequences are exploitable security bugs?
It’s an example of why this problem is so annoying: C++ wants you to use std::vector (just like Rust wants you to use Vec) but in a GC’d world you just created a landmine that can easily blow up in your face.
-
-
What's wrong with the Oilpan approach? (Honest question. I don't understand the limitations of Oilpan as they don't seem to be documented.)
-
In particular, I think one aspect of the Oilpan approach is "Don't use `Vec` or `std::vector`; you must use the Oilpan counterpart."
-
Same with Servo. That’s the ergonomic tax I was talking about though: I want something automatic that lets you write regular old Rust or C++, not weird-Servo-DOM-flavored Rust. I may not ever get what I want, but it doesn’t stop me from wanting it :)
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.