News for hackers. Stuff that matters.
Re:Catching use-after-move C++ bugs with Clang's consumed an... by markdoubleyou on Wednesday July 10, 2019 @01:46PM (#20404398)
This stuff has been out there for a long time, but it's never become popular outside of outside of safety-critical or high-integrity systems. Examples include:

Microsoft's C/C++ annotations: https://docs.microsoft.com/en-us/visualstudio/code-quality/u...

Ada's ranges: https://en.wikibooks.org/wiki/Ada_Programming/Types/range

Fun stuff to learn about in theory, but, unless you're working at a place where formal verification is part of the culture, good luck selling these tools to upper management.

More resources discussed here: http://highscalability.com/blog/2018/9/19/how-do-you-explain...

Re:Catching use-after-move C++ bugs with Clang's consumed an... by sfkdjf9j3j on Wednesday July 10, 2019 @02:16PM (#20404711)
Ada's ranges are runtime checked right? How would you do this in a compiler?
Re:Catching use-after-move C++ bugs with Clang's consumed an... by olliej on Wednesday July 10, 2019 @03:26PM (#20405525)
Ada checks all arithmetic - the compiler can elide bounds checks if it can statically verify that no out of range error can happen, but if it can’t verify statically you get bounds checks at runtime.
Re:Catching use-after-move C++ bugs with Clang's consumed an... by gameswithgo on Wednesday July 10, 2019 @08:28PM (#20407999)
a little of both iirc