Nullness - option<> must be indicated as nullable in IL for C# consumers #17528
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
❗ Release notes required
|
vzarytovskii
approved these changes
Aug 13, 2024
7 tasks
vzarytovskii
approved these changes
Aug 16, 2024
psfinaki
approved these changes
Aug 19, 2024
This was referenced Aug 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
F#
option<>Has UseNullAsTrueValueAttribute on it, making the representation ofNonenullin IL.Therefore, even if the type is not considered
null(assignment, pattern matching, ..) in F#, it must reported as nullable for C# consumers.This can be also demonstrated at runtime by using the reflection helpers at
NullabilityInfoContext(test added).This covers all types marked as UseNullAsTrueValue as well as (~legacy, not recommended under
--checknulls+) types marked with AllowNull.