Way to scope dagger subcomponents via backstack

Hi,
this is a uninformed question, but, often times I hear that "screen" frameworks provide a mechanism of creating and storing a subcomponent instance, and then clearing it on popping

Anybody tried something like this with Conductor?

Start by reviewing Conductor's backstack and lifecycle behavior, focusing on how components are created and cleared when screens are popped. Determine whether scoped Dagger subcomponents can follow that lifecycle; done would require a defined, documented approach or a clear statement of the supported limitation.

Written by the indexing model from the issue text.