Use readonly members for debugger record types #1013
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
**Bug** Small code annoyance: in the debugger we have a lot of boilerplate code to implement readonly properties. **Fix** Just use readonly member values for this pattern. We already do this in a number of places in debugger.
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.
Bug
Small code annoyance: in the debugger we have a lot of boilerplate code to implement readonly properties by using a readonly member backing.
Fix
Just use readonly member values for this pattern. We already do this in a number of places in debugger. Also, marked some of these classes as sealed.
This make the code briefer and reduces duplication, making updates and understanding easier.