1. All uses of `as` for type conversion. 2. All the syntactic sugar for raw pointers, especially the pointer dereferencing operator. 3. Most of the OS-related functionality of libstd, esp. `std::net`, esp. `ToSocketAddrs`. Most languages have the same problematic stuff though.
-
-
-
This is fair, and I agree with #1 and #3 (though not #2). All comparatively minor stuff though.
- 2 more replies
New conversation -
-
-
very easy: start with borrow checker
-
... of course it stops being Rust at that point but alas
- 14 more replies
New conversation -
-
-
when said as praise, "the simplicity of..." should end in something better than "C" >_<
-
"The simplicity of C" - yes I love the formally defined, totally unambiguous, popular and well understood semantics of volatile, static, inline, bitfields and packing.
End of conversation
New conversation -
-
-
I think we don’t need the borrow checker. Making good encapsulation, and not permitting using internal values by reference would remove the need of borrow checker.
-
This is debunked by basically the entire history of programming. Thread safety and memory safety without the borrow checker and without GC does not happen and telling programmers to do it better isn't going to change that.
- 9 more replies
New conversation -
-
-
Universal impl Trait is the most obvious to me, but that's a drop in the complexity bucket
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.