Clean up DocumentContext a little#12990
Merged
davidwengier merged 7 commits intodotnet:mainfrom Apr 2, 2026
Merged
Conversation
Contributor
This was referenced Apr 3, 2026
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
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.
We currently have
DocumentContext,DocumentSnapshotand of course Roslyn'sDocument, and now that we don't have any indirection needs, these are rife for improvement. This is not that, but perhaps a step on the path.It started because I noticed the
HACK:comment, which is now easily resolvable, and then I pulled on the thread a little, because I figure if there are less things on these types, then it makes it easier to reason about their usage.