FarNet 6.0.15 (next) will use nullable reference types

[nightroman]

FarNet 6.0.15 enables and maintains nullable reference types (NRT).
See Nullable reference types.

In theory this does not change much for modules at runtime. But internal FarNet
code tweaks may have subtle effects. Please report unwanted changes or bugs.

It is up to modules to enable NRT or not. If a module enables NRT then FarNet
API now provides reasonable nullability hints at compile time as warnings.

Work in progress

At this moment not all API may reflect the actual nullability correctly.
Work is still in progress. Please report noticed discrepancies, e.g.

• a method or property with non-nullable value actually returns null
• a parameter or property is non-nullable but you may pass null
• etc.

Potential drawbacks

There should not be any changes at runtime, in theory. If FarNet changes formal
nullability of some API items then modules should work as usual. But compiling
modules may produce new warnings.

Just do not enable NRT in modules if you would like to avoid warnings.

If a module already uses NRT... well, it has to deal with warnings.

PowerShellFar

PSF does not enable NRT yet, to be continued. This is not very important:

• PSF does not contribute much to the documented API FarNetAPI.chm
• NRT in API is not really useful for scripts without compiler checks

[nightroman]

Update

• FarNet 6.0.16 has some more NRT adjusted/corrected
• PowerShellFar 6.0.18 now uses NRT as well (though this does not change much)