This is a live coding exercise. Without Foundation's NotificationCenter, design and implement a small EventBus in Swift that subscribes and publishes by name. Tell me how you handle lifetime and the unsubscribe API so no handler is left behind after an observer goes away.
A dictionary of name to [subscription], subscribe returns a token, and observers are held weakly or removed when the token is released. When the token deinits, the subscription drops out on its own.
ArchitectureMultiple choiceBasics
Which of these statements about Foundation's NotificationCenter are correct? Select all…
#observer #notification
ArchitectureMultiple choiceAdvanced
In this Coordinator implementation, LoginCoordinator stays in memory after the login flow…
#weak
ArchitectureShort answerIntro
When do you use a singleton in an iOS app, and what's the problem with it?
#thread-safety
ArchitectureShort answerIntro
Can you explain the Delegate pattern that shows up all over UIKit?
#notification