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

feat(maitake): introduce a separate maitake-sync crate #462

Merged
merged 12 commits into from
Sep 4, 2023

Conversation

hawkw
Copy link
Owner

@hawkw hawkw commented Sep 4, 2023

The maitake crate provides async synchronization primitives in a
maitake::sync module. These APIs don't require the rest of the
runtime, and would be nice to be able to use in other crates. maitake
is not yet published to crates.io, as it contains Git-only dependencies.
However, the sync module can be implemented entirely using published
code, and therefore, a crate containing only maitake::sync could be
published.

This branch introduces a new maitake-sync crate, containing the
synchronization primitives from maitake::sync. The maitake::sync
module now re-exports maitake-sync, so there should be no impact for
existing uses of the crate. The new maitake-sync crate can easily be
published to crates.io, and depended on from released code.

@hawkw hawkw enabled auto-merge (squash) September 4, 2023 19:13
@hawkw hawkw merged commit 8d85472 into main Sep 4, 2023
@hawkw hawkw deleted the eliza/maitake-sync branch September 4, 2023 20:24
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.

1 participant