You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For most cases, enabling nullable annotations context should be straightforward. However, there are some functions where special annotations are required. These cases are more fully described by the corresponding documentation on migration strategies.
If interested, I am happy to work on preparing a PR to enable this ... just let me know.
The text was updated successfully, but these errors were encountered:
Enabling non-nullable reference types requires explicit update to the .csproj file. This is done for backwards-compatibility.
Current compiler warnings
Three files are currently trying to use the non-nullable reference types feature, without the feature actually being enabled. The compiler emits the following warning for each of Enumerate/BlockEnumerator.cs,
Enumerate/MergeEnumerator.cs, and
Enumerate/TableEnumerator.cs:
See C# documentation for details.
See also relevant stackoverflow thread.
Caveats (click to expand)
For most cases, enabling nullable annotations context should be straightforward. However, there are some functions where special annotations are required. These cases are more fully described by the corresponding documentation on migration strategies.
If interested, I am happy to work on preparing a PR to enable this ... just let me know.
The text was updated successfully, but these errors were encountered: