c_sharp_exports.rst: add complex getter/setter note #8859
Merged
Conversation
This file contains hidden or 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
AThousandShips
added
enhancement
topic:dotnet
area:manual
raulsntos
reviewed
Jan 29, 2024
31
force-pushed
the
dev/31/backing-export-behavior
branch
2 times, most recently
from
b2ea82a to
4d300af
Compare
31
force-pushed
the
dev/31/backing-export-behavior
branch
from
4d300af to
cfa455e
Compare
mhilbrunner
approved these changes
Feb 1, 2024
Member
|
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
I think that with an example saying you can use a backing field, it's worth pointing out this quirk. It doesn't come up that often but people do run into it. I think that explaining that the C# code is analyzed also helps make some other behavior more reasonable without needing to point it out: e.g. that constructors aren't involved.