It's related to Coordinator, but a Coordinator is usually also responsible for constructing the destinations in question, which in turn means that it--and not the call site--is the only entity that's aware of the view's dependencies and requirements.

This solution requires that knowledge in each and every call site.

And that leads to the drawbacks I mentioned. Not being able to use NavigationLink(value:) is a biggy.