this post was submitted on 19 Mar 2024
145 points (92.9% liked)
Programming
16760 readers
234 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 [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
$100 says his response boils down to "just don't write unsafe code"
Edit: It did. He also said C++ is working to implement optional safety features, but tl;dr:
And the modern guidelines are mostly an unenforced list of things not to do.
doesnt enforce memory safety damn all these stupid devs dont know how to write memory-safe code!!!
Even following the guidelines, modern C++ is just a huge pile of half-finished ideas. It goes pretty well for the first few hundred lines of code, and then you hit a very basic problem where the solution is "yes this will work great in C++26, if the proposal doesn't get delayed again".
You're making it pretty clear that you are completely oblivious to what C++ is, what are the differences between C++ versions, and what are the real world issues solved by each new version.
I would ask you to clarify your persona clams by providing a concrete example to back each of your statements, but I know you have none.
Lol okay. Here are some concrete examples I don't have:
Templates as basic generics
Templates for metaprogramming
Safe union types
Error handling
std::expected
eventually approved, similar to Rust's Result type, but with no equivalent to the '?' operator to make the code readablestd::expected
has even stabilised, but will probably not be available for 10 yearsSubtype polymorphism deprecated
References
auto
variable in a template, and instead of giving a helpful type error it implicitly coerced a new copy of my vast memory buffer into existenceI think if you consider anything post C++03 (so C++11 or newer) to be "modern C++" then Concepts must be the top example, doesn't it?
Counting from C++0x that's almost a decade of waiting.
Pretty sure this is a No true Scotsman moment. (I've always wanted to bring this fallacy up but I never knew when lol)
Just another c++ boomer too scared to adapt and switch to rust.