-
Notifications
You must be signed in to change notification settings - Fork 0
feat(p1a): curate XmlReader/XmlWriter/JsonDocument as owned factories #153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please don't classify all
XmlReader.Create/XmlWriter.Createoverloads as pure factories without also handling their disposable inputs. The extractor's escape pass removes any candidate disposable passed as an argument, and this factory branch later emits only an acquire for the reader/writer; invar fs = File.OpenRead(p); var xr = XmlReader.Create(fs); xr.Dispose();,fsis dropped from tracking even thoughXmlReaderSettings.CloseInputdefaults to false, so the caller-owned stream leak is suppressed. Either restrict the matched overloads or model these inputs as borrowed/non-escaping.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch — fixed in 83edff6. You're right that the Stream/TextReader/TextWriter overloads don't own their input (CloseInput/CloseOutput default false, and JsonDocument.Parse never closes its stream), so classifying them as pure factories let the escape pass drop the caller-owned input and suppress its leak.
Went with precision over recall (the project's stated floor): the new factory branch now declines the claim whenever any argument resolves to an IDisposable (
!AnyDisposableArgument). SoXmlReader.Create(fs)/JsonDocument.Parse(stream)are no longer treated as factories —fsstays tracked and its leak is reported — while the common no-disposable-arg overloads (XmlReader.Create("file.xml"),JsonDocument.Parse(jsonString)) still resolve and catch a dropped reader/document. Modelling the input as borrowed-non-escaping (your option b) would keep recall on those overloads too, but it's a deeper escape-pass change; I took the conservative narrowing for now. No dotnet locally, so CI (golden C# / leak extractor / corpus benchmark) verifies the build + specificity.Generated by Claude Code