Pitch: Syntactic sugar for circumventing closure capture lists

[sveinhal (Svein Halvor Halvorsen)]

@GetSwifty

And while your ViewController is still in memory, you don't have any guarantees the structure/components around it are. So if you do something like pass a function rather than have a [weak self] closure, you can have a lot of weird things happen.

Sounds like buggy code. Using weak captures doesn’t really fix the underlying problem.

Poorly designed code doesn’t get better with default weak over default strong. You’re just swapping one set of problems for another.

And changing it is source breaking.