3 ms·
ISO Core C++ is trying to do something like this. They have to, in order to count on the properties of "const" for their static safety analysis. (I have my res
by pcwalton 11y ago
ISO Core C++ is trying to do something like this. They have to, in order to count on the properties of "const" for their static safety analysis.
(I have my reservations about whether ISO Core C++ with the lifetime profile really qualifies as C++ anymore due the massively backwards incompatible nature of the changes, but it'll be interesting nonetheless.)
- twoodfin 11y agoCan you link to more information about this? Googling for "c++ core lifetime profile" just takes me to the Core Guidelines. Is the idea that they'll codify a bunch of static analysis that disallows problematic constructs & patterns? Could implementers then add something like Rust's ownership checks (assuming full source visibility)?
- pjmlp 11y agoYes. Microsoft has delivered a beta version of it with VS 2015 Update 1. Clang guys are improving clang-tidy for similar errors. Check Herb Sutter's talk at CppCon 2015.
- gaul 11y agoCppCon 2015: Herb Sutter "Writing Good C++14... By Default": https://youtu.be/hEx5DNLWGgA https://youtu.be/hEx5DNLWGgA Sutter comments on const_cast around 11m15s.
- steveklabnik 11y agoMy sibling commentators have given you good links, but it's worth noting that these systems and Rust have a lot of differences. For example, they're explicitly not trying to tackle data races, and the way that they work is different. I'm excited to see this all play out though!