diff options
| author | Matthias Krüger <476013+matthiaskrgr@users.noreply.github.com> | 2025-03-22 21:34:40 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-03-22 21:34:40 +0100 |
| commit | 3f59916a3025f949c0cdfbfa3d8d373092caee4d (patch) | |
| tree | 43d6260425719b0f4f54b608b7f0c37a59969fb1 /compiler/rustc_parse_format/src/lib.rs | |
| parent | 7372f2812b241c1d5901b3a3d5664328d3b913bb (diff) | |
| parent | 110f1fe17f370c88548187397b425e1d256cced6 (diff) | |
| download | rust-3f59916a3025f949c0cdfbfa3d8d373092caee4d.tar.gz rust-3f59916a3025f949c0cdfbfa3d8d373092caee4d.zip | |
Rollup merge of #138822 - moxian:unlock, r=joshtriplett
De-Stabilize `file_lock` This reverts #136794 FCP on the tracking issue (#130994) passsed successfully https://github.com/rust-lang/rust/issues/130994#issuecomment-2646158607 but there are now concerns about the suitability of the proposed API (https://github.com/rust-lang/rust/issues/130994#issuecomment-2734608366) On zullip it was [suggested](https://rust-lang.zulipchat.com/#narrow/channel/219381-t-libs/topic/File.3A.3Atry_lock.20API.3A.20Result.3Cbool.3E/near/506823067) that it would be better to temporarily(?) destabilize the feature ASAP to buy us some more time reflecting on the API. This PR implements the revert. The feature is not currently on beta (https://github.com/rust-lang/rust/blob/beta/library/std/src/fs.rs#L672) so a beta backport is not yet neccessary. If this revert is accepted, the tracking issue (#130994) should be reopened
Diffstat (limited to 'compiler/rustc_parse_format/src/lib.rs')
0 files changed, 0 insertions, 0 deletions