social.noyu.me

“why don't languages like c++ and java have multiple constructors? they're so useful! i love that rust has multiple constructors!”

the finger curls on the monkey's paw

and i find out about the hell of objective-c designated initialisers

@hikari Swift at least adds a static type system for initializers to make all of the best practices around them work consistently and soundly.

@porglezomp @hikari In case this wasn’t sarcasm what it actually does is everyone adds fatalError in init(coder:)

@saagar @hikari oh I was thinking sincerely about the Swift-first classes that aren’t forced to inherit the ObjC soup

@porglezomp @saagar @hikari We have lost the magic of Good Interface Builder with Live View Objects in the style of the Steve Jobs Calculator Constructor (implemented with some truly wild object substitution shenanigans) but are still forced to carry “every AppKit and UIKit type claims to be NSCoding”.

@jrose @porglezomp @saagar @hikari having written that deprecation message, with 15 years of love in my heart, let me say: good riddance

@jrose @porglezomp @saagar @hikari but yeah, those conformances are forever

@millenomi @jrose @porglezomp @hikari I have discovered that if you mark all your initializers as convenience inits it probably breaks something or the other but you don’t have to interact with NSCoding directly

@saagar @jrose @porglezomp @hikari yup, correct. It means that you are inheriting your designated initializer situation from your superclass, that is, you support using your superclass’s initializers to produce a fully functional object of _your_ subclass, and so the init(coder:) of your superclass is good enough for your subclass too.

The moment you add a designated init, the init(coder:) of your superclass isn’t sufficient anymore and you have to do both (if only to fatalErrror out).

@millenomi @jrose @porglezomp @hikari Yeah so the lie here is that calling the superclass’s designated initializer is not actually going to provide a functional object because I do all that work in the convenience initializer

@saagar @millenomi @porglezomp @jrose btw interface builder can call init on your class if you prefer that to initWithCoder:, but I assume it can't connect outlets and stuff if you do (or can it 🤔)

@hikari @saagar @porglezomp @jrose it will set your outlets anyway. but why use IB at this point when SwiftUI is just so much better on every important level

@millenomi @saagar @porglezomp @jrose what if i am coding for 2008's best mobile operating system. what then

@hikari @millenomi @porglezomp @jrose How’s your Java

@hikari @millenomi @porglezomp @jrose You know you want to emulate it…