As the runtime continues to evolve, I think it might be a good idea to take advantage of new features of each release of .NET.
One of the features released in C# 8.0 was nullable reference types. NRTs are designed to improve the intent of the C# code by forcing developers to handle all the null references and therefore avoid NullReferenceException crashes.
Practically, this is not needed for the operation of this runtime, because even if the proxy calls code that was compiled with the feature enabled, it still checks the returned object against null.
This would also make it easier to avoid null de-referencing while performing bigger refactors in the future.
If main contributors think this is not worth it, I can close this issue and move on, no worries.
As the runtime continues to evolve, I think it might be a good idea to take advantage of new features of each release of .NET.
One of the features released in C# 8.0 was nullable reference types. NRTs are designed to improve the intent of the C# code by forcing developers to handle all the null references and therefore avoid
NullReferenceExceptioncrashes.Practically, this is not needed for the operation of this runtime, because even if the proxy calls code that was compiled with the feature enabled, it still checks the returned object against
null.This would also make it easier to avoid null de-referencing while performing bigger refactors in the future.
If main contributors think this is not worth it, I can close this issue and move on, no worries.