Lucas Lois

To be honest I was guided by clippy to make that change. But, as seen on the rustonomicon, "If there is exactly one input lifetime position (elided or not), that...

What I could try out is removing the 'b annotation on the output to ensure it is the same as the one on the Input (as it was originally)

I began implementing this but as I thought more about it... were should this be implemented? It might be possible to simplify the whole graph, for example (`self.graph`), but perhaps...

Sure, I thought about the performance cost but I guessed the cost wouldn''t be much and the benefit of abstraction could facilitate the implementation of the `simplify` algorithm. However, it...

@TaipanRex you might want to check this out

So, I've been playing with that. It seems like `StaticParamList` adds an ` | undefined` to nested navigators, which does not happen on the "common" navigator definitions. ```ts const DemoStackToNest...

Seems to stem from `ParamsForScreen` having an explicit `| undefined` on it: https://github.com/react-navigation/react-navigation/blob/8e7ac4f18545887b905f921df469dbf69d7951c7/packages/core/src/StaticNavigation.tsx#L49 This type, ultimately, seems to only be used for defining `StaticParamList`. Any reason not to make that...

> Because you can navigate to a screen without needing to specify any child screens - which renders the initial route defined in the navigator. The types need to handle...

Okay, I've figured this one out. I'm now doing a "two way extends" with `NavigatorScreenParams` and `ParamList[RouteName]` (+ a utility `NotUndefined` type), which afaik covers all cases. Not particularly fond...

I'll work on this!