Nullable reference types

[CoskunSunali]

Does it make sense to enable nullable reference types for DryIoc at some point in the future? One thing that makes me think it is not going to be easy is because some methods change nullability based on their parameters. E.g.

Resolve<T>(IfUnresolved.ReturnDefault) // mightbenull, will return default/null without throwing

Resolve<T>(IfUnresolved.ReturnDefaultIfNotRegistered) // mightbenull, might return default/null without throwing

Resolve<T>(IfUnresolved.Throw) // notnull, would throw otherwise

I had to wrap around DryIoc for some reason and I solved the issue by using the following methods.

#nullable enable

public T? GetService<T>()
{
    return _resolverContext.Resolve<T>(IfUnresolved.ReturnDefaultIfNotRegistered);
}

public object? GetService(Type serviceType)
{
    return _resolverContext.Resolve(serviceType, IfUnresolved.ReturnDefaultIfNotRegistered);
}

[return: NotNull]
public T GetRequiredService<T>()
{
    return _resolverContext.Resolve<T>(IfUnresolved.Throw)!; // notice the exclamation mark
}

public object GetRequiredService(Type serviceType)
{
    return _resolverContext.Resolve(serviceType,  IfUnresolved.Throw);
}