[PATCH] D36067: [analyzer] Create infrastructure for organizing and declaring analyzer configs.

[Gábor Horváth via Phabricator via cfe-commits]

xazax.hun added a comment.

I like the directions of this patch.
In general, I am in favor of explicitly registering the options from user defined checkers. 
But changing a config option will now break the command line compatibility, so I wonder how do we want to handle this:

- Have a list of no-op configs that we accept but warn that it has been replaced/removed?
- Just do not care and break compatibility?
- Something else?

I have a wishlist for this feature but I am perfectly fine to only address those in follow-up patches:

- Ability to set descriptions and maybe default values in the Checkers.td
- Command line argument to dump the list of options with descriptions (and defaults)


https://reviews.llvm.org/D36067