Expand description
Target-conditional Send/Sync bounds (Send native, vacuous on wasm).
Target-conditional Send/Sync bounds: real on native, vacuous on wasm32.
The pipeline runs as one logical task on every target. On native that task
should still be Send so a work-stealing executor (e.g. multi-threaded
tokio) can spawn and migrate it like any other task. On wasm32 there is
only one thread and JS handles (JsValue) are !Send, so the same bounds
must vanish. These aliases express “Send where it exists” once, so the rest
of the codebase is written a single time.
Traits§
- Maybe
Send Sendon native targets; no requirement onwasm32.- Maybe
Send Sync Send + Syncon native targets; no requirement onwasm32.