Skip to content
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

De-Stabilize file_lock #138822

Merged
merged 1 commit into from
Mar 23, 2025
Merged

De-Stabilize file_lock #138822

merged 1 commit into from
Mar 23, 2025

Conversation

moxian
Copy link
Contributor

@moxian moxian commented Mar 22, 2025

This reverts #136794

FCP on the tracking issue (#130994) passsed successfully #130994 (comment) but there are now concerns about the suitability of the proposed API (#130994 (comment))

On zullip it was suggested 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

@rustbot
Copy link
Collaborator

rustbot commented Mar 22, 2025

r? @jhpratt

rustbot has assigned @jhpratt.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs Relevant to the library team, which will review and decide on the PR/issue. labels Mar 22, 2025
@moxian
Copy link
Contributor Author

moxian commented Mar 22, 2025

r? joshtriplett

@rustbot rustbot assigned joshtriplett and unassigned jhpratt Mar 22, 2025
@joshtriplett
Copy link
Member

Looks good, r=me when CI passes.

I'm noting here that reverting this is not making any particular commitment for what the API should be, or whether it should be changed at all, just preserving option value for potentially changing it before stabilization. The change will need to be a team decision; I'm merely approving the revert to give time for that decision.

@moxian
Copy link
Contributor Author

moxian commented Mar 22, 2025

I don't think i have the perms, but
@bors r=joshtriplett rollup

@bors
Copy link
Contributor

bors commented Mar 22, 2025

@moxian: 🔑 Insufficient privileges: Not in reviewers

@bors
Copy link
Contributor

bors commented Mar 22, 2025

@moxian: 🔑 Insufficient privileges: not in try users

@jhpratt
Copy link
Member

jhpratt commented Mar 22, 2025

@bors r=joshtriplett rollup

@bors
Copy link
Contributor

bors commented Mar 22, 2025

📌 Commit 110f1fe has been approved by joshtriplett

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 22, 2025
bors added a commit to rust-lang-ci/rust that referenced this pull request Mar 22, 2025
…iaskrgr

Rollup of 8 pull requests

Successful merges:

 - rust-lang#138018 (rustdoc: Use own logic to print `#[repr(..)]` attributes in JSON output.)
 - rust-lang#138294 (Mark some std tests as requiring `panic = "unwind"`)
 - rust-lang#138468 (rustdoc js: add nonnull helper and typecheck src-script.js)
 - rust-lang#138675 (Add release notes for 1.85.1)
 - rust-lang#138765 (Fix Thread::set_name on cygwin)
 - rust-lang#138786 (Move some driver code around)
 - rust-lang#138793 (target spec check: better error when llvm-floatabi is missing)
 - rust-lang#138822 (De-Stabilize `file_lock`)

r? `@ghost`
`@rustbot` modify labels: rollup
@bors bors merged commit 3f59916 into rust-lang:master Mar 23, 2025
6 checks passed
rust-timer added a commit to rust-lang-ci/rust that referenced this pull request Mar 23, 2025
Rollup merge of rust-lang#138822 - moxian:unlock, r=joshtriplett

De-Stabilize `file_lock`

This reverts rust-lang#136794

FCP on the tracking issue (rust-lang#130994) passsed successfully rust-lang#130994 (comment) but there are now concerns about the suitability of the proposed API (rust-lang#130994 (comment))

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 (rust-lang#130994) should be reopened
@rustbot rustbot added this to the 1.87.0 milestone Mar 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-libs Relevant to the library team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants