Description
In our codebase, the current dependency container can accept resolution requests for types not yet registered in the container. In our code it returns a "future", but I think to be more correct, we'd return a Promise from the container that would be fulfilled in the future either 1) when the type is registered or 2) on first non-forward resolution (the user should be able to choose between policies)

Alternate solutions
I worked around this by using a separate service within the container to track outstanding resolution requests and resolve them per policy when the types are registered with the container.