4 ms·
The Core Guidelines are an attempt at this, but it’s not fully safe. Safer, which matters! But not safe. There isn’t really any useful safe subset of C++. If t
by steveklabnik 8y ago
The Core Guidelines are an attempt at this, but it’s not fully safe. Safer, which matters! But not safe.
There isn’t really any useful safe subset of C++. If there were, Rust may never have been created in the first place.
- ncmncm 8y agoThis is not, in fact, the case. Back when Rust was begun, it had some merit, but C++ is a rapidly moving target. C++ still does not have an absolutely safe subset, but it has a safe-enough subset, and plenty of other merits that will ensure its continued competitiveness. Rust will continue improving, too, and someday may be as expressive as C++ is today, or perhaps even as expressive as C++ is then. That will be a good day, although by then some other language will be on the rise, its users hoping to displace C++ and, given enough luck and hard work, Rust. V could be interesting.
- pjmlp 8y agoStill, C++ is good enough for the unsafe low level bindings of a Java/.NET application. Until Rust's tooling catches up with C++/CLI, C++/CX, C++/WinRT + .NET or Java + C++ (Eclipse/Netbeans/Oracle Studio), CUDA, Unreal/Unity, GLSL/HLSL/Metal Shaders allow for, it will stay as a safe way to write CLI apps and a couple of UNIX libs. I like the language and advocate it often, but I am also very pragmatic regarding the areas I and customers work on.