Presumably these issues could be detected at runtime by having the compiler add checking logic into dev/debug builds. The static approach used here may have th

Presumably these issues could be detected at runtime by having the compiler add checking logic into dev/debug builds. The static approach used here may have the advantage of giving a more categorical assurance, i.e. one that doesn't depend on the particular behaviour exercised at runtime, but it requires annotations, meaning that: 1. It can't be used on an existing codebase lacking these annotations 2. It trusts the programmer to get the annotations right (I'm not particularly well informed of recent developments in C++, perhaps such runtime instrumentation already exists?)