Cargo Features
[dependencies]
veilid-tools = { version = "0.4.1", default-features = false, features = ["rt-async-std", "rt-tokio", "rt-wasm-bindgen", "veilid_tools_android_tests", "veilid_tools_ios_tests", "tracing", "debug-locks"] }
- default = rt-tokio
-
The
rt-tokio
feature is set by default wheneverveilid-tools
is added without
somewhere in the dependency tree.default-features = false - rt-async-std = async-std
-
Enables async_std of async_executors, smol_socket of rtnetlink =0.13.1
Affects
native::block_on
… - rt-tokio default = tokio, tokio-stream, tokio-util
-
Enables tokio_io, tokio_timer and tokio_tp of async_executors, tokio_socket of rtnetlink =0.13.1
Affects
native::block_on
… - rt-wasm-bindgen
-
Enables bindgen and timer of async_executors
- veilid_tools_android_tests
-
Enables paranoid-android
- veilid_tools_ios_tests
-
Enables oslog, tracing, and tracing-oslog ^0.1.2
- tracing
-
Enables tracing and tracing-subscriber, tracing of tokio
- debug-locks
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.
- async-std not wasm32 rt-async-std?
- tokio-stream not wasm32 rt-tokio
- tokio-util not wasm32 rt-tokio
- tokio not wasm32 rt-tokio tracing?