Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adjust FS-1075 : nullable interop - apply rule to all arguments, not just optional ones #9316

Merged
merged 5 commits into from
May 29, 2020

Conversation

dsyme
Copy link
Contributor

@dsyme dsyme commented May 27, 2020

This is a potential adjustment to RFC FS-1075 which is currently in preview

The adjustment is based on this usability feedback, which indicates that we should extend this to interoperating with non-optional nullable-typed arguments

@dsyme dsyme force-pushed the feature/nullable-interop branch from 16eb5a5 to 6f0332d Compare May 27, 2020 18:38
@cartermp cartermp requested review from TIHan and KevinRansom May 28, 2020 15:26
@cartermp cartermp changed the title Adjust FS-1075 : nullable interop Adjust FS-1075 : nullable interop - apply rule to all arguments, not just optional ones May 28, 2020
Copy link
Contributor

@cartermp cartermp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My approval here is for the scenario and test cases, which I feel are adequate. Not for the implementation.

This change definitely makes using packages like Microsoft.Data.Analysis more pleasant.

@KevinRansom KevinRansom merged commit 3d19992 into dotnet:master May 29, 2020
nosami pushed a commit to xamarin/visualfsharp that referenced this pull request Feb 23, 2021
…just optional ones (dotnet#9316)

* adjust non-optional nullable interop

* adjust non-optional nullable interop

* fix error messages

* fix baseline

* fix baseline
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants