default warning sets
mobileink opened this issue · comments
Currently each(?) rule has a configurable warnings default, e.g. @ocaml//executable:warnings=-1-2-3
Default is set to @1..3@5..28@30..39@43@46..47@49..57@61..62-40
Question: is that a good default? Should the rules even set a default?
One option is to define several 'warning sets' as config setting rules, so users can select by meaningful label. E.g. @ocaml//warnings:default set to the above, @ocaml//warnings:foo set to some other list, etc.
Insofar as warnings form semantic groupings, we could have one label per group (concept), and then we could compose warning sets.