No, it's actually a good idea. That way I can programmatically check if any error is going to be reported inside of a method or function that's being silenced.

No, it's actually a good idea. That way I can programmatically check if any error is going to be reported inside of a method or function that's being silenced. And, on top of that, override the silencing within a method or function directly. Using an established interface provides me with a ton of options ... options I wouldn't have if it did some sort of internal voodoo.