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.
std.fs: support
Lock.none
on Windows #21306New 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
base: master
Are you sure you want to change the base?
std.fs: support
Lock.none
on Windows #21306Changes from all commits
683dbbd
8a4d319
43ac4df
da2f6c7
a07bfbd
2f4cfce
edfdd9c
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.
Should this change also be made in
unlock()
?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.
unlock
can't return an error.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.
Then it seems questionable to me that we're doing it here. If we're worried that the OS might become able to return an error here in the future, the same concern surely applies to
unlock()
? Are we just crossing our fingers and hoping that such an error will be safe to ignore inunlock()
?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 think so; same sort of thing with
File.close
. I agree that it seems strange forunlock
, not sure that should really count as "resource deallocation."FWIW, there's exactly one instance of
File.unlock
in a defer that I could find:zig/lib/std/crypto/tls/Client.zig
Lines 1512 to 1513 in 5b4759b