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

[Raphael Isemann via Phabricator via cfe-commits]

teemperor added a comment.

In https://reviews.llvm.org/D36067#825867, @xazax.hun wrote:

> 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?


Don't have a preference here, but adding a forwarding config that also emits a warning should be easy to do.

> 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)

Yes, I would prefer having this in follow up patches. I tried to keep this as a minimal starting example because this currently blocks @yamaguchi 's GSoC project for bash completion. There we want to complete the values for `-analyzer-config` and we currently don't have a good way to get a complete list of available configs from the driver :).


https://reviews.llvm.org/D36067