search for: someflag

It seems relevant to point out there have been several efforts over the years to solve this problem by eliminating the static initializers in LLVM and migrate cl::opts to storing their values in a context object. One of those efforts was made by me back in 2014 (see https://reviews.llvm.org/D6207 <https://reviews.llvm.org/D6207>). One of the perennial problems with cl::opt is that many of

...Mueller's post on strong typedef [1]. The Problem ----------- As noted on a side-thread of the variable naming convention change, LLVM has a number of places where function parameter semantics are unclear at the point of use [2]. To compensate, much code exists in this style: foo(arg1, /* SomeFlagName = */true); Functions with, for example, two boolean parameters are often called as: foo(arg1, /* Flag1Name = */true, /* Flag2Name =*/false); Unfortunately, it is easy to mix this up unintentionally: foo(arg1, /* Flag1Name = */false, /* Flag2Name =*/true); The above may or may not be a...