wacore 0.7.0

Core WhatsApp protocol implementation without runtime dependencies
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

//! Conditional `Send + Sync` bound.
//!
//! Native builds drive the client across multi-threaded receive lanes, so any
//! trait object stored on it must be `Send + Sync`. wasm32 is single-threaded
//! and its callbacks may hold `!Send` JS handles (see
//! [`crate::msg_secret::OriginalMessageResolver`]), so the bound is dropped
//! there. The blanket impls keep this transparent: on native every
//! `Send + Sync` type already satisfies it, on wasm every type does.

#[cfg(not(target_arch = "wasm32"))]
pub trait MaybeSendSync: Send + Sync {}
#[cfg(not(target_arch = "wasm32"))]
impl<T: Send + Sync + ?Sized> MaybeSendSync for T {}

#[cfg(target_arch = "wasm32")]
pub trait MaybeSendSync {}
#[cfg(target_arch = "wasm32")]
impl<T: ?Sized> MaybeSendSync for T {}

/// `Send`-only variant for values that cross task boundaries but are never
/// shared by reference (closures, futures). Same wasm rationale as
/// [`MaybeSendSync`].
#[cfg(not(target_arch = "wasm32"))]
pub trait MaybeSend: Send {}
#[cfg(not(target_arch = "wasm32"))]
impl<T: Send + ?Sized> MaybeSend for T {}

#[cfg(target_arch = "wasm32")]
pub trait MaybeSend {}
#[cfg(target_arch = "wasm32")]
impl<T: ?Sized> MaybeSend for T {}