Memory Leaks about coordinator-example HOT 2 CLOSED

@wtsnz, I found solution for your example. Just declare your Optional delegates as a weak, like so:

weak var delegate: NewOrderCoordinatorDelegate? = nil

(actually, nil here isn't required, cause Optionals are nil by default)

...and so:

weak var delegate: DrinkTypeControllerDelegate?
weak var delegate: SnackTypeViewControllerDelegate?
weak var delegate: SplashViewControllerDelegate?

And we get absolutely another picture:

All generations made in the following order:

1. root -> add (cancel) -> root (x5 times);
2. root-> add (coffee) -> add (muffin) -> root (x5 times);
3. etc.

What do you think about it? :)

from coordinator-example.

Hey @remenkoff!

Thanks so much for this, awesome investigation work there! You're absolutely right, I forgot to mark the delegates as weak in this example 🙃

I'll update the example code with the changes!

from coordinator-example.