145
C++ creator rebuts White House warning
(www.infoworld.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Mar 2024
145 points (92.9% liked)
Programming
17314 readers
92 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
It's because it's hard to make them correct. It's not any harder to write it in rust than in C. Just C lets you do it wrong
That's not right.
Try and write a mutable doubly linked list in Rust and you will find that it's problematic for the borrow checker.
Search online and you will find solutions that work around this using 'RefCell' (to delegate mutable borrows to runtime), or raw pointers with 'unsafe'.
Both RefCell and unsafe are features of the language. That's like saying python's OOP sucks if you don't use the
classkeyword.I'm not saying it sucks. I'm saying it can be less straight-forward than conventional languages, even for experienced programmers.
The borrow checker is fantastic, but there's no doubt that it requires a new way of thinking if you've never seen Rust before.