36
The empire of C++ strikes back with Safe C++ blueprint (www.theregister.com)
submitted 2 years ago* (last edited 2 years ago) by cmeerw@programming.dev to c/cpp@programming.dev
36 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[-] lysdexic@programming.dev -3 points 2 years ago

If you could reliably write memory safe code in C++, why do devs put memory safety issues intontheir code bases then?

That's a question you can ask to the guys promoting the adoption of languages marketed based on memory safety arguments. I mean, even Rust has a fair share of CVEs whose root cause is unsafe memory management.

[-] FizzyOrange@programming.dev 2 points 2 years ago

No it doesn't, that's bullshit.

[-] sukhmel@programming.dev 2 points 2 years ago

Well, there is cve-rs, just sayin'

[-] robinm@programming.dev 3 points 2 years ago

The fact that rustc has bugs (which is what cve-rs exploit) doesn't invalidate that rust the language is memory safe.

this post was submitted on 17 Sep 2024
36 points (95.0% liked)

C++

2357 readers
1 users here now

The center for all discussion and news regarding C++.

Rules

founded 3 years ago
MODERATORS
lysdexic@programming.dev
Nihili0@programming.dev