-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
suggestion: move Deno.flock()
and friends
#22178
Comments
This seems reasonable 👍 we should add new methods to |
Cool. Please assign this issue to me. |
This was referenced Feb 2, 2024
bartlomieju
pushed a commit
that referenced
this issue
Feb 4, 2024
littledivy
pushed a commit
that referenced
this issue
Feb 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I suggest we remove the following APIs in favour of new
Deno.FsFile
methods:Deno.flock()
>Deno.FsFile.lock()
Deno.flockSync()
>Deno.FsFile.lockSync()
Deno.funlock()
>Deno.FsFile.unlock()
Deno.funlockSync()
>Deno.FsFile.unlockSync()
The reasoning is the same as other recent deprecations; they accept
rid
parameters, and we want to make these private.Alternatively, if these aren't seen as useful, we can remove them. We should be fine to move or remove them, as they are part of the unstable API.
The text was updated successfully, but these errors were encountered: