C++

1811 readers

1 users here now

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

Rules

Respect instance rules.
Don't be a jerk.
Please keep all posts related to C++.

founded 2 years ago

MODERATORS

lysdexic

[email protected]

Nihili0

The empire of C++ strikes back with Safe C++ blueprint (www.theregister.com)

submitted 3 months ago* (last edited 3 months ago) by cmeerw to c/cpp

37 comments fedilink hide all child comments

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

[–] FizzyOrange 8 points 3 months ago (2 children)

Yeah but I have written a lot of Rust and I have yet to use a single unsafe block.

Saying "but.. unsafe!" is like saying Python isn't memory safe because it has ctypes, or Go isn't memory safe because of its unsafe package.

[–] [email protected] 1 points 3 months ago (1 children)

You don't have to use unsafe C++ functions either

C++ is technically safe if you follow best practices

The issue, to me, is that people learn older versions of the language first, and aren't aware of the better ways of doing stuff.

IMO people should learn the latest C++ version first, and only look at the older types of implementation when they come across them

[–] FizzyOrange 2 points 3 months ago (1 children)

C++ is technically safe if you follow best practices

Yeah but it's virtually impossible to reliably follow best practices. The compiler won't tell you when you're invoking UB and there is a lot of potential UB in C++.

So in practice it is not at all safe.

[–] [email protected] 4 points 3 months ago

I agree

I was only adding my opinion (that people should try to always use the latest version of C++, which is inherently safer, but still not 100% safe)

[–] [email protected] -5 points 3 months ago

See my reply to funtrek's reply.