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

Update Rust crate async-lock to v3 #20

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Oct 24, 2023

This PR contains the following updates:

Package Type Update Change
async-lock dependencies major 2.7.0 -> 3.0.0

Release Notes

smol-rs/async-lock (async-lock)

v3.4.0

Compare Source

  • Port to event-listener v5.0.0. (#​74)

v3.3.0

Compare Source

  • Add a forget() method for semaphore guards. (#​73)
  • Increase MSRV to v1.60. (#​75)

v3.2.0

Compare Source

  • Add missing methods for blocking on locking with types wrapped in Arc (#​71).

v3.1.2

Compare Source

  • Bump event-listener to version v4.0.0. (#​69)

v3.1.1

Compare Source

  • Add a note to the documentation comparing this crate against libstd's locks. (#​58)

v3.1.0

Compare Source

  • Add a Default implementation for OnceCell (#​63).

v3.0.0

Compare Source

  • Breaking: Add an enabled-by-default std feature that allows using this crate without the standard library. (#​43)
  • Support blocking and non-blocking operations on the same locks. (#​56)
  • Switch to a more efficient event notification mechanism. (#​43)

v2.8.0

Compare Source

  • Fix a bug where the SemaphoreGuard::acquire_arc future would busy wait under certain conditions (#​42).
  • Add a Semaphore::add_permits() function to increase the number of available permits on the semaphore (#​44).
  • Make RwLockReadGuard covariant over its lifetime (#​45)
  • Add RwLockReadGuardArc, RwLockWriteGuardArc, and other reference counted guards for the RwLock type (#​47).
  • Loosen the Send/Sync bounds on certain future types (#​48).
  • Fix UB caused by the MutexGuardArc::source function allowing the user to drop an object in a different thread than the one it was acquired in (#​50). This is a breaking change, but in the name of soundness. Therefore it doesn't break any valid behavior.
  • Fix a bug where this crate would not compile properly on wasm64 (#​51).

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/async-lock-3.x branch 2 times, most recently from b12ec01 to ba07ecb Compare November 19, 2023 20:00
@renovate renovate bot force-pushed the renovate/async-lock-3.x branch from ba07ecb to 71d2d9d Compare November 24, 2023 19:41
@renovate renovate bot force-pushed the renovate/async-lock-3.x branch from 71d2d9d to 536f943 Compare December 2, 2023 20:29
@renovate renovate bot force-pushed the renovate/async-lock-3.x branch from 536f943 to 05dc062 Compare January 10, 2024 07:03
@renovate renovate bot force-pushed the renovate/async-lock-3.x branch from 05dc062 to 9043403 Compare May 5, 2024 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants