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.
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
Add ProcessStartInfo constructor that accepts IEnumerable<string> arguments #86346
Add ProcessStartInfo constructor that accepts IEnumerable<string> arguments #86346
Changes from 3 commits
f52d103
5c925c7
dbf7815
e9c62f9
7623449
bd45642
1b5e494
2e0a9a0
356bd75
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
devdoc
is relic of the past (it's not documented anywhere, you had no chance to know about it), please use standard summary tagsThere 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.
Why should we allow for nulls in the new API?
Since the argument is not marked as nullable, the method should throw for nulls.
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.
I can move these checks into the new
ProcessStartInfo
ctorruntime/src/libraries/System.Diagnostics.Process/src/System/Diagnostics/Process.cs
Lines 1328 to 1331 in af1171b
I'm a little worried about consistency. The other ctors for
ProcessStartInfo
are not throwingArgumentNullException
andProcess.Start(string fileName, IEnumerable<string> arguments)
is the only overload of that method that throws.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.
This is true, but they are old and we can't easily change their behavior. For the new APIs, we either allow for nulls by making an argument nullable, or we don't and throw. Since the API was not approved as nullable (no ?), we should throw. By doing that we send a clear message in the API contract: nulls are not allowed, if you have a
null
arguments, just don't use this API.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.
nit: it could be simplified