Arithmetic operators: mention possible casting with compound assignment #11898
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
Member
|
closing and reopening for a new build while I review. |
BillWagner
approved these changes
Apr 18, 2019
Member
BillWagner
left a comment
BillWagner
left a comment
There was a problem hiding this comment.
Thanks for these additions @pkulikov It's an important clarification.
I'll 
now.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
As an operation performed as it is and the same operation performed as a part of compound assignment might end up with "inconsistent" results, I think it's worth to mention possible casting involved in compound assignment with arithmetic operators.
Supported by dotnet/samples#825
Also, added
checkedanduncheckedto thedisplayNamefield in the TOC entry for arithmetic operators