Refactor lazy initialization to use field backed property declarations#27413
Open
xtqqczze wants to merge 1 commit into
Open
Refactor lazy initialization to use field backed property declarations#27413xtqqczze wants to merge 1 commit into
xtqqczze wants to merge 1 commit into
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR refactors a set of lazily-initialized collections on InitialSessionState to use C# field-backed property declarations, reducing boilerplate while preserving the existing thread-safe initialization approach via Interlocked.CompareExchange.
Changes:
- Replaced explicit private backing fields (
_assemblies,_types, etc.) with field-backed properties using thefieldkeyword. - Consolidated the previous
if (x == null) CompareExchange(...)pattern into expression-bodied properties for multiple collections/dictionaries/sets.
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
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.
No description provided.