Resolving interfaces with contravariant type parameter fails with RegisteringImplementationNotAssignableToServiceType error

[PhilippK13]

Hi.

I have the following hierarchy(simplified for brevity):

public class Settings
{
  public string Address {get; set;}
}

public class ExtraSettings : Settings
{
  public string Key {get; set;}
}

public interface IValidator<in T>
{
  public bool IsValid(T settings);
}

public abstract class AbstractValidator<T> : IValidator<T>
{
  public bool IsValid(T settings)
  {
    return true;
  }
}

public class SettingsValidator : AbstractValidator<Settings>
{
  
}

I'm trying to make this to work, but getting a RegisteringImplementationNotAssignableToServiceType error:

var genericType = typeof(IValidator<>).MakeGenericType(typeof(ExtraSettings));
var services = new ServiceCollection(); // Microsoft.Extensions.DependencyInjection

services.AddSingleton<IValidator<ExtraSettings>, SettingsValidator>();
  
var container = new Container();
var adaptedContainer = container.WithDependencyInjectionAdapter(services); // this throws
IServiceProvider serviceProvider = adaptedContainer;

var validator = serviceProvider.GetService(type);

The following is the message of the exceptin throw:
code: Error.RegisteringImplementationNotAssignableToServiceType; message: Registering implementation type SettingsValidator is not assignable to service type IValidator<ExtraSettings>.

However, this code(without DryIoC) works as expected:

var genericType = typeof(IValidator<>).MakeGenericType(typeof(ExtraSettings));
var services = new ServiceCollection(); // Microsoft.Extensions.DependencyInjection

services.AddSingleton<IValidator<ExtraSettings>, SettingsValidator>();

var serviceProvider = services.BuildServiceProvider();
var validator = serviceProvider.GetService(type);

I don't think I'm violating any Type rules, so I expect the DryIoC to work just fine. Is this a bug or am I missing something?

[dadhi]

@PhilippK13 Thanks for reporting and code repro.
It seems that I have already fixed the problem in context of the #418 . But I did not release the fix yet. Hoping to release Today.