The base idea is that we may want to have a kind of configuration for some lints, embedded in the attribute. This would piggy-back on the existing attribute syntax.
There are actually two stages of expansions of this idea: In the first stage we still only allow one
deny attribute per lint per item/module, in the second state we’d allow multiples, which would undoubtedly make the lint API more complex, but allow for things like
#![warn(deprecation)] #![allow(deprecation(foo, bar))]. However this could also be written as
Motivation: We currently have a few lints which rely on whitelists that could be extended by configuration; also we have a few lints split into multiple lints so we can carve out niches for different cases that allow different levels. Those could be re-combined with configuration.
What do you folks think?