> feels like both a horror show and an exercise in futility
Can you expand on that - I don't understand the horror or the futility. It certainly is a bit of code smell - but only because there is no quick way to harden the implementations. But I rather have a clear and stable API and fix the the implementation along the way than to leak the problems to the API consumer and just document it. For me it's not about "appease some tool" it's just that the tool has revealed a problem and we have to decide how to deal with this in the future. cheers, Torsten
