A recent review emphasized the preference to use DefaultBool instead of
bool for checker options. This change is a NFC and cleans up some of the
instances where bool was used, and could be changed to DefaultBool.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
A recent review emphasized the preference to use DefaultBool instead of bool for checker options.
What I wanted to highlight is that we should aim for consistency. We should either use that everywhere or nowhere.
To be fair, we should probably use raw bools instead.
They could not only default to false, but to true as well.
In addition to this, we should prefer the c++ way of initializing these at the declaration directly to either of those values.
IMO we don't need this DefaultBool abstraction.
Hi @steakhal, I believe I've addressed the comments. Please have a look and let me know if this is what you were after. Best!
Good stuff. Update the summary and title, and I think good to go.
In addition to this, we should do something similar with the rest of the checker options and initialize them at the declaration. But that is a different story.