Swift: Simple, Safe, Inflexible

At some point you'll end up with breakage unless doing this _causes_ the subclasses to implement the initializer with super (if not already present), not just require it. I don't really like that, but it might actually work.

You shouldn't really get to mess with someone else's implementation... that's partly what subclassing is for and that's where it should get fixed. I'm not really familiar with the barrier here since Swift isn't available on my platform, but I can't think of a reason for it to be such a problem, unlike the the other road.

It's certainly possible. It wouldn't always work easily (for example, in the NSDate example, which uses private subclasses in its class cluster model). But it would be better than what exists now.