Struct dharitri_wasm::types::MultiArg5

pub struct MultiArg5<T0, T1, T2, T3, T4>(pub (T0, T1, T2, T3, T4));

Tuple Fields

0: (T0, T1, T2, T3, T4)

Implementations

impl<T0, T1, T2, T3, T4> MultiArg5<T0, T1, T2, T3, T4>

pub fn into_tuple(self) -> (T0, T1, T2, T3, T4)

Trait Implementations

impl<T0, T1, T2, T3, T4> ContractCallArg for &MultiArg5<T0, T1, T2, T3, T4>

where T0: ContractCallArg, T1: ContractCallArg, T2: ContractCallArg, T3: ContractCallArg, T4: ContractCallArg,

fn push_async_arg(&self, serializer: &mut ArgBuffer) -> Result<(), SCError>

impl<T0, T1, T2, T3, T4> ContractCallArg for MultiArg5<T0, T1, T2, T3, T4>

where T0: ContractCallArg, T1: ContractCallArg, T2: ContractCallArg, T3: ContractCallArg, T4: ContractCallArg,

fn push_async_arg(&self, serializer: &mut ArgBuffer) -> Result<(), SCError>

impl<T0, T1, T2, T3, T4> DynArg for MultiArg5<T0, T1, T2, T3, T4>

where T0: DynArg, T1: DynArg, T2: DynArg, T3: DynArg, T4: DynArg,

fn dyn_load<I, D>(loader: &mut D, arg_id: ArgId) -> Self

where I: TopDecodeInput, D: DynArgInput<I>,

impl<FA, T0, T1, T2, T3, T4> EndpointResult<FA> for MultiArg5<T0, T1, T2, T3, T4>

where FA: EndpointFinishApi + Clone + 'static, T0: EndpointResult<FA>, T1: EndpointResult<FA>, T2: EndpointResult<FA>, T3: EndpointResult<FA>, T4: EndpointResult<FA>,

fn finish(&self, api: FA)

impl<T0, T1, T2, T3, T4> From<(T0, T1, T2, T3, T4)> for MultiArg5<T0, T1, T2, T3, T4>

fn from(tuple: (T0, T1, T2, T3, T4)) -> Self

Converts to this type from the input type.

impl<T0, T1, T2, T3, T4> TypeAbi for MultiArg5<T0, T1, T2, T3, T4>

where T0: TypeAbi, T1: TypeAbi, T2: TypeAbi, T3: TypeAbi, T4: TypeAbi,

fn type_name() -> String

fn provide_type_descriptions<TDC: TypeDescriptionContainer>( accumulator: &mut TDC )

A type can provide more than its own description. For instance, a struct can also provide the descriptions of the type of its fields. TypeAbi doesn’t care for the exact accumulator type, which is abstracted by the TypeDescriptionContainer trait.