@mikeash What strikes me about this is my long experience w/ working around bugs in C frameworks which have no swizzling of any kind.
-
-
-
@mikeash As well as many bugs I've worked around in Apple frameworks that never needed (or allowed) subclassing. Just a tool; not the tool. -
@mikeash I hate prevent the optimizer from doing its job just because someone somewhere might someday need to hack around something. - View other replies
-
@cocoaphony I agree, the language thing is not really a big deal to me, but rather the discussion around it.
-
-
-
@mikeash I assume this is about SE-0117. The “we won’t be able to fix bugs” argument is kind of moot at this point. `final` already exists - View other replies
-
@Javi It's not so much about the proposal as it is about Apple's attitude that the right way to deal with bugs is to report them. -
@mikeash I haven’t read that from them. If I do, I’ll feel exactly the way you do. More openness would go great ways towards this.
-
-
@mikeash for final in swift, is there no backdoor option? 'cuz if it's truly enforced, that's super painful and short-sighted
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
mikeash
Rob Napier
Javi
Steven L