Replace terniary null checks with coalescing. #19222
Merged
Conversation
This file contains 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
penev92
previously approved these changes
Mar 7, 2021
pchote
force-pushed
the
more-null-coalescing
branch
from
8f901fe
to
a2eba92
Compare
|
Updated. |
teinarss
approved these changes
Mar 8, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Continuing with the theme of syntax updates. This contains a mix of automated fixups (no behaviour changes) and some manual changes where we introduce harmless or wanted behaviour changes in cases like
tooltip != null ? tooltip.Name : armyUnit.ActorInfo.Name→tooltip?.Name ?? armyUnit.ActorInfo.Namewhich now fall back to theActorInfoiftooltipwas valid buttooltip.Namereturned null.