This makes sense for objects that can enter an equivalent invalid state after successful construction as the result of a method call (e.g. a file or stream). F

This makes sense for objects that can enter an equivalent invalid state after successful construction as the result of a method call (e.g. a file or stream). For objects that don't have that property, you're just exchanging one kind of badness in the design for a different but ultimately equivalent badness.