-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Improve File::set_times
error handling
#101675
Conversation
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
(rust-highfive has picked a reviewer for you, use r? to override) |
@joshtriplett #102368 has now been merged. Is there anything else in this PR that needs addressing? |
Looks good. Thank you! @bors r+ |
📌 Commit b8ae84c2f0e7f43521fb20bf385bb0aad4b9d509 has been approved by It is now in the queue for this repository. |
⌛ Testing commit b8ae84c2f0e7f43521fb20bf385bb0aad4b9d509 with merge 51446c90ae1a022044c794d72326091c011bf446... |
💔 Test failed - checks-actions |
This comment has been minimized.
This comment has been minimized.
…temTime` doesn't fit into the required type
b8ae84c
to
c66860a
Compare
@joshtriplett I've fixed the unused import that caused the build to fail. |
@bors r+ rollup |
…iaskrgr Rollup of 3 pull requests Successful merges: - rust-lang#101675 (Improve `File::set_times` error handling) - rust-lang#102500 (Remove `expr_parentheses_needed` from `ParseSess`) - rust-lang#102533 (rustdoc: remove unused CSS selector `a.source`) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Makes
File::set_times
return an error if theSystemTime
cannot fit into the required type instead of panicking inFileTimes::set_{accessed,modified}
. Also makesFile::set_times
return an error on Windows if either of the passed times are0xFFFF_FFFF_FFFF_FFFF
, as the documentation forSetFileTime
states that this will prevent operations on the file handle from updating the corresponding file time instead of setting the corresponding file time to that value.Tracking issue: #98245