Cargo Features
yaar-lock has no features set by default.
[dependencies]
yaar-lock = { version = "0.2.1", features = ["full", "nightly", "sync", "future", "os", "bench_sync", "bench_async"] }- full = future, os, sync
- nightly
- sync bench_sync? full? future? = lock_api
-
Main features for yaar-lock
Affects
yaar-lock::sync… - future bench_async? full? = futures-intrusive, sync
-
Affects
yaar-lock::future… - os bench_async? bench_sync? full? = libc
-
Enables handleapi, libloaderapi and winbase of winapi
Affects
future::ResetEvent,future::WaitForEventFuture,future::Mutex,future::MutexGuard,future::MutexLockFuture,future::Semaphore,future::SemaphoreReleaser,future::SemaphoreAcquireFuture… - bench_sync = criterion, crossbeam-utils, num_cpus, os, parking_lot, sync
-
Used for controlling dev dependencies
- bench_async = async-std, criterion, future, num_cpus, os
-
Enables std of futures-intrusive ^0.3, rt-threaded and sync of tokio ^0.2
Features from optional dependencies
In crates that don't use the dep: syntax, optional dependencies automatically become Cargo features. These features may have been created by mistake, and this functionality may be removed in the future.
- lock_api sync?
-
Enables lock_api ^0.3
lib depedencies
- futures-intrusive bench_async? future?
-
Enables futures-intrusive ^0.3
- num_cpus bench_async? bench_sync?
-
Enables num_cpus
dev dependencies
- parking_lot bench_sync?
-
Enables parking_lot ^0.10
- crossbeam-utils bench_sync?
-
Enables crossbeam-utils ^0.7
- async-std bench_async?
- tokio bench_async?
-
Enables tokio ^0.2
- libc unix os?
- winapi win os?
- criterion bench_async? bench_sync?
-
Enables criterion ^0.3