[Poll] Do people care about separated EmptyXXXBlock, ThrowXXX and CatchXXX rules?

Now every case has it’s own rule - example EmptyFunctionBlock or ThrowRuntimeException. As each rule visits a whole kotlin file, there is kind of an overhead when ~10 nearly the same rules visit this file.

I favored the above approach in the beginning of detekt because it allowed out-of-the-box-yaml-configuration for each of this rules.

To remove this overhead, there are two options + leaving as it is is option three. Please thumps up or down to vote on the options.

[arturbosch]

That’s because I’m on vacation ! 😄

[arturbosch]

Option 3: Like option 2 but with configurable flavours

style:
  ...
  EmptyBlock:
    active: true/false
    allowEmptyFunction: true/false
    allowEmptyCatch: true/false
    allowEmptyElse: true/false
  ...
potential-bugs:
  ...
  TooGeneralExceptionIsThrown:
    active: true/false
    exceptions: "RuntimeException, IndexOutOfBoundException, MyOwnNeedSubclassingException"
  TooGeneralExceptionIsCatched:
    active: true/false
    exceptions: "RuntimeException, IndexOutOfBoundException, MyOwnNeedSubclassingException"
  ...