Coordinator memory
In this Coordinator implementation, LoginCoordinator stays in memory after the login flow finishes. Which is the most likely cause?
final class AppCoordinator {
var children: [Coordinator] = []
func showLogin() {
let child = LoginCoordinator(nav: nav)
child.onFinish = { self.children.removeAll { $0 === child } }
children.append(child); child.start()
}
}Pick one
Memory and ARCShort answerBasics
A view controller doesn't seem to leave memory after you close its screen. How would you …
#retain-cycle #weak
Memory and ARCShort answerAdvanced
From the moment an object's last strong reference goes away until the memory is actually …
#weak #lifecycle
TestingMultiple choiceExpert
Which are problems with the test class below? Select all that apply. …
#memory #lifecycle
ArchitectureShort answerAdvanced
What problem is the Coordinator in MVVM-C meant to solve?
#coordinator