The implementation may be asynchronous, so that a facility whose construction depends on a value only another
service can supply, such as a client keyed from a secret vault, is still resolved by a synchronous lookup: bound
implementations are constructed and awaited as the execution opens, under the terms detailed at Executor.
Important
An implementation is held to the same all-or-nothing requirement as any other factory, and an
asynchronous one is the most exposed to it: whatever it awaits may be awaited again from scratch, as the run that
started it may be abandoned before it records an instance.
Binds an implementation to a service.
The implementation may be asynchronous, so that a facility whose construction depends on a value only another service can supply, such as a client keyed from a secret vault, is still resolved by a synchronous lookup: bound implementations are constructed and awaited as the execution opens, under the terms detailed at Executor.
An implementation is held to the same all-or-nothing requirement as any other factory, and an asynchronous one is the most exposed to it: whatever it awaits may be awaited again from scratch, as the run that started it may be abandoned before it records an instance.