Mathias LANG

Yes! I've been wanting this for a while, but the problem is that it's a breaking change for library users. Instead adding a `final` function that forwards to the implementation...

> Ah, you mean people who inherit from `AbstractFallbackPackageSupplier`. > > Hmm yes, likely not many, but still. Actually, changing the return type of `fetchPackageRecipe` means anyone implementing the `PackageSupplier`...

@skoppe : If you can find a small change to make (e.g. the `[]` => `null` changes) and PR it separately, that would whitelist you for future CI runs of...

> I think I need to add a [...] Yes, that's what I was recommending. `final` because "function body only allowed in `final` functions in interface".

I don't think we should support v2.076, but we should support the last 10 versions. That looks like a rather simple fix.

It's not a simple fix. Since we are using `std.sumtype`, which is in Phobos only since v2.097.0, it creates a lot of issues. Using `dyaml.stdsumtype` leads to other problems.

> Using `dyaml.stdsumtype` leads to other problems. `-mv` is never the answer. And as I mentioned: > Using `dyaml.stdsumtype` leads to other problems.

This is a great feature. The behavior of `dub` is not compatible with e.g. Docker and path dependency. In our use case, we have submodules as path dependencies, and we...

In general, I'd like us to be able to express the default behavior using the configuration. Meaning that there could be a configuration the user can enter that allows them...

> The contained "version" can change at any moment by checking out a different commit, so it needs to be re-checked on every run. But we don't. We determine the...