Jon Pretty

@puffnfresh but the thing is I *want* the null rule 99% of the time, I just want to be able to override it explicitly when necessary

@pelotom macros will let you use WartRemover for specific code blocks and even whole classes when macro annotations land.

@puffnfresh again, though, the converse is more desirable... opt-out of WartRemover, not opt-in

@pelotom I understand but I also think that opt-out partially defeats the purpose of a linter.

@puffnfresh @pelotom can I not say "apply wartremover universally except here and here"?

@dibblego @pelotom nope.

@puffnfresh I'm with @dibblego. I'd like to be able to apply it everywhere except places I'm stuck dealing with bad apis. @pelotom

@coltfred @dibblego @pelotom are separate SBT project(s) for wrapping bad stuff really a problem?