Avoid boxing booleans during tracing and when setting bool?
properties
#10884
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.
This should be only merged after #10711 so we don't have to unnecessarily add the usings for
KnownBoxes
.Gonna draft it for the same reason so that I can do an additional sweep once it is merged.
Description
Avoids boxing booleans in a few more cases than already done in #10628 and #10711.
I didn't opt-in for making a
nullable<bool>
helper for DPs as its not that prevalent and saves a few bytes.Customer Impact
Less boxed booleans on the heap, less memory usage.
Regression
No.
Testing
Local build.
Risk
Low.
Microsoft Reviewers: Open in CodeFlow