Skip to content

Conversation

@daxian-dbw
Copy link
Member

Reverts #13277

Quote from #13277 (comment)

As for this PR, the rest of maintainers discussed about it offline, and we all agree that we shouldn't force is null over == null. We think they clearly are appropriate in different scenarios. Changes in this PR will not only result in conflicts in other existing PRs, but also raise disputes in future contributions because people will continue to use == null and argue for it. So we decided to revert this PR.

@daxian-dbw
Copy link
Member Author

@PoshChan Please remind me in 1 hour

@daxian-dbw daxian-dbw merged commit 4b9b078 into master Jul 30, 2020
@daxian-dbw daxian-dbw deleted the revert-13277-isnull branch July 30, 2020 23:06
@PoshChan
Copy link
Collaborator

@daxian-dbw, this is the reminder you requested 1 hour ago

@daxian-dbw daxian-dbw added the CL-CodeCleanup Indicates that a PR should be marked as a Code Cleanup change in the Change Log label Jul 30, 2020
@daxian-dbw daxian-dbw added this to the 7.1.0-preview.7 milestone Jul 30, 2020
@TravisEz13 TravisEz13 modified the milestones: 7.1.0-preview.7, 7.1.0-preview.6 Aug 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CL-CodeCleanup Indicates that a PR should be marked as a Code Cleanup change in the Change Log

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants