News for hackers. Stuff that matters.

A comment on Borrow Checking, RC, GC, and Eleven Other Memory Safety Approaches. Parent comment

Re:Borrow Checking, RC, GC, and Eleven Other Memory Safety A... by PeterWhittaker on Thursday December 19, 2024 @08:06AM (#42461063)
The first part - that the Rust borrow checker and overall memory model ensures thread/async safety - is true. I cannot speak to the second part - that other systems don't have this assurance.
[ Parent | on HN ]
Re:Borrow Checking, RC, GC, and Eleven Other Memory Safety A... by tialaramex on Thursday December 19, 2024 @08:33AM (#42461222)
Just the borrowck isn't enough, you need the Send and Sync marker traits. Marker traits are something lots of languages could do but they'd be useless (or always unsafe) without a lot of other machinery Rust had already.
[ Parent | on HN ]
Re:Borrow Checking, RC, GC, and Eleven Other Memory Safety A... by kibwen on Thursday December 19, 2024 @10:47AM (#42462576)
And Sync might just be there for performance, I think you could get away with only Send if you didn't mind some additional copying?
[ Parent | on HN ]
Re:Borrow Checking, RC, GC, and Eleven Other Memory Safety A... by DanielHB on Thursday December 19, 2024 @08:43AM (#42461290)
> that other systems don't have this assurance

My understanding is that most (all?) GC languages are memory safe, but do not ensure statically verifiable thread safety at all. Like Java, Go, C#, Python, etc.

[ Parent | on HN ]