`InvokeAs` problems about do HOT 5 OPEN

1- I think you should just call do.Invoke[I] instead of do.InvokeAs[i], since your not performing interface matching here. I will improve the error message.

2- I'm not sure to understand the issue here. Your example output seems valid to me.

from do.

While i review comments on #45, I'm linking your issue to #45 (comment)

To describe the feedback from @mbark:

• We provide *MyServiceImplem
• Then invoke IMyService
• We implement a *MyServiceMock via an override for test purposes.

Problem: do.InvokeAs will pick a random implementation of IMyService

from do.

Possible solutions:

• invoke the latest injected service -> I don't like it, since the service injection order might be non-determinist
• use do.OverrideNamedValue(i, do.NameOf[IMyService](), NewMyServiceMock) -> not developer friendly
• use explicit aliases: do.AsNamed() -> might trigger error on override

@d-enk suggested reporting an error when multiple services match the interface.

Also, I would point out that since services injected in IoC containers are opaque, invoking an interface instead of a struct might lead to loading the wrong service if method signatures overlap. In that situation, an explicit alias is safer: do.AsNamed()

from do.

Another option, maybe you just need a separate method that returns a list of all match?
And in InvokeAs allow only one

looks like related #33

from do.

to fix 1 problem #81

from do.