[PATCH] D53692: [analyzer] Evaluate all non-checker config options before analysis

[Artem Dergachev via Phabricator via cfe-commits]

NoQ added a comment.

I guess i'm running out of steam for today :)

> `Opts.shouldDoThat()` -> `Opts.ShouldDoThat.getValue()`

Is this really unavoidable? Like, what makes them optional when they're always non-optional? Maybe just somehow prevent un-eagerly-initialized AnalyzerConfig from appearing anywhere in the program?


https://reviews.llvm.org/D53692