Rob Bygrave

> Currently, I have to wrap the generic types in a non-generic wrapper class to wire across modules. That sounds like a concrete class being used across a module boundary...

> an example of wrapping? I meant a _real world_ example - as in, we are using tight coupling between 2 modules with a **_concrete_** class (and not an interface)....

There were 2 regressions for "Partial Compile" starting in version `10.0-RC5` including `10`, `10.1`, `10.2-RC*`. The regressions were only fixed in `10.2`. > and I don't see the error when...

So I'm 100% sure of this yet. ## The Problem The problem this is looking to address relates to multi-module wiring when there becomes 2 candidates to wire and how...

What was the resolution here? Why did this issue get closed?

I think you should re-open it. It isn't the case the no one cares but more people are busy and you just need to wait a bit longer before this...

> maybeLoad An alternative would be to add a `loadMaybe(...)` that takes resource and file and for the `load(...)` methods to fail on missing resource. This might be preferrable in...

That is excellent insight / feedback - thanks!! > ... an idea of the disturbing level complexity you can get with LoadFlags Yes, re-enforces the idea that we should try...

We have got the ServiceLoader change in now so that completes all the tasks mentioned here. So now I think it's just a matter of confirming we are all good...

Just to say 4.0 is actually released. I assumed we were all good and released it (quite a few days ago now).