This is why I've started just using interfaces for Utility classes. You get the same benefit, except it blows up at compile time instead of at runtime.
Not a great idea because now people can subclass your util class and start passing it around. I'd argue you're abusing the type system by doing what you suggest, and would always favour a final class with a private constructor that throws an exception.
I'll say the same thing I said in the last post - how is the first thing an error? Imagine we do it your way and have a class StaticThings. Then we have another object that uses it in a method:
class SpaceShuttle { void doSomethingThatCannotFail() { new StaticThings() {}.doSomething(); }
Now this code blows up at runtime, even though there is no actual problem. There's no real problem in any of the scenarios, by as long as we're signaling at compile time, it's fine to be a little overly paranoid. Once we get to runtime that's much riskier.
EDIT: missed the bit about the class being final. Why is the exception even necessary in this case? It can't ever be invoked.
11
u/CubsThisYear Mar 03 '17
This is why I've started just using interfaces for Utility classes. You get the same benefit, except it blows up at compile time instead of at runtime.