"Rust's compiler prevents common bugs" So does skill. No offense to you, but, this trope is getting so tiresome. If you like the language then go ahead and use it. What is it with the rust crowd that they have to come acrosslike people trying to convert your religion at your front door?

you are viewing a single comment's thread
view the rest of the comments

[–] smiletolerantly@awful.systems 119 points 2 days ago (18 children)

if your skill is so great that you would never cause the kinds of bugs the rust compiler is designed to prevent, then it will never keep you from compiling, and therefore your complaint is unnecessary and you can happily use rust
if you do encounter these error messages, then you are apparently not skilled enough to not use rust, and should use rust

In summary: use rust.

[–] tatterdemalion@programming.dev 22 points 2 days ago (1 children)

Your first point is not true. There are valid uses of memory sharing that rust will reject.

[–] smiletolerantly@awful.systems 5 points 2 days ago (2 children)

Curious what you are talking about. Multi-threaded sharing of memory for example is also easy with rust, it just doesn't let you wrote and read at the same time, and so on.

[–] qaz@lemmy.world 1 points 1 day ago (1 children)

Classic example: A linked list

[–] smiletolerantly@awful.systems 0 points 1 day ago (1 children)

... are entirely possible, even if rarely the right choice.

[–] qaz@lemmy.world 1 points 1 day ago* (last edited 1 day ago)

With unsafe, but how can you write a double linked list in safe rust? (without indices)

[–] sukhmel@programming.dev 7 points 2 days ago

Off the top of my head, single-threaded writing to the same memory from different fields of a struct. Not to mention self-referencing like if you want to hold a buffer and have different views into it in the same structure.

load more comments (16 replies)