Skip to content

Use nullable backing field to check for default value #21351

New issue

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

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

Already on GitHub? # to your account

Merged
merged 1 commit into from
Jun 21, 2020
Merged

Conversation

ajcvickers
Copy link
Contributor

Fixes #15182

This allows a null backing field to be used for a non-nullable property while at the same time checking the backing field for null in order to determine if a property value has been set.

@ajcvickers ajcvickers requested a review from a team June 20, 2020 19:38
@ajcvickers ajcvickers force-pushed the Nule0620 branch 2 times, most recently from f05d268 to 8ab6526 Compare June 20, 2020 23:01
Fixes #15182

This allows a null backing field to be used for a non-nullable property while at the same time checking the backing field for null in order to determine if a property value has been set.
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Enable nullable backing field pattern for store-generated defaults
2 participants