Module multiversx_sc_scenario::imports

source ·
Expand description

Imports normally needed in integration tests, grouped together.

Re-exports§

Modules§

Macros§

Structs§

Enums§

Constants§

Traits§

  • Add
    The addition operator +.
  • AddAssign
    The addition assignment operator +=.
  • AnnotatedValue
    Describes a value can also have a custom representation in a mandos scenario.
  • ArgNestedTuple
    Models an argument tree of the form (arg1, (arg2, ... (argn, ()))), used for retrieving endpoint arguments.
  • BitAnd
    The bitwise AND operator &.
  • BitAndAssign
    The bitwise AND assignment operator &=.
  • BitOr
    The bitwise OR operator |.
  • BitOrAssign
    The bitwise OR assignment operator |=.
  • BitXor
    The bitwise XOR operator ^.
  • BitXorAssign
    The bitwise XOR assignment operator ^=.
  • ContractBase
    Interface to be used by the actual smart contract code.
  • ContractCall
    Defines a contract call object, which is the basis for all calls to other contracts.
  • ContractCallBaseDeprecated
    Converts into a legacy contract call.
  • Div
    The division operator /.
  • DivAssign
    The division assignment operator /=.
  • ErrorApiImpl
  • ExternallyMergeable
    Used when merging is done through an external SC call. Generally, these only need to have the same token ID, with different nonces.
  • FixedSupplyToken
  • InterpretableFrom
  • IntoMultiValue
    Defines conversion of a type to its multi-value representation.
  • ManagedBufferBuilderImpl
  • ManagedType
    Commonalities between all managed types.
  • ManagedTypeApi
  • ManagedVecItem
    Types that implement this trait can be items inside a ManagedVec. All these types need a payload, i.e a representation that gets stored in the underlying managed buffer. Not all data needs to be stored as payload, for instance for most managed types the payload is just the handle, whereas the mai ndata is kept by the VM.
  • ManagedVecItemNestedTuple
    Syntactic sugar, that allows us to more easily represent composite payloads as nested tuples.
  • ManagedVecItemPayload
    Describes the binary represetnation of a ManagedVecItem.
  • ManagedVecItemPayloadAdd
    Describes concatantion of smaller payloads into a larger one.
  • Mergeable
    Used for types that can be merged locally.
  • Mul
    The multiplication operator *.
  • MulAssign
    The multiplication assignment operator *=.
  • NestedDecode
    Trait that allows zero-copy read of value-references from slices in LE format.
  • NestedEncode
    Trait that allows zero-copy write of value-references to slices in LE format.
  • ProxyArg
    Trait that is automatically implemented for all types that are allowed as proxy inputs.
  • ProxyObjBase
  • ProxyObjNew
  • RHList
  • RHListAppendNoRet
  • RHListAppendRet
  • RHListExec
    Indicates how result processing will undergo for an ensemble of result handlers.
  • RHListItem
    Result handler list item.
  • RHListItemExec
    Indicates how result processing will undergo for one specific result handler.
  • RegisterCodeSource
    Used when registering a contract for debugging.
  • Rem
    The remainder operator %.
  • RemAssign
    The remainder assignment operator %=.
  • SCError
    Any type that implements this trait can be used to signal errors when returning from a SC endpoint.
  • ScenarioTxEnv
    Designates a tx environment suitable for running scenarios locally.
  • ScenarioTxRun
    Provides a run method for transactions and steps.
  • Shl
    The left shift operator <<. Note that because this trait is implemented for all integer types with multiple right-hand-side types, Rust’s type checker has special handling for _ << _, setting the result type for integer operations to the type of the left-hand-side operand. This means that though a << b and a.shl(b) are one and the same from an evaluation standpoint, they are different when it comes to type inference.
  • ShlAssign
    The left shift assignment operator <<=.
  • Shr
    The right shift operator >>. Note that because this trait is implemented for all integer types with multiple right-hand-side types, Rust’s type checker has special handling for _ >> _, setting the result type for integer operations to the type of the left-hand-side operand. This means that though a >> b and a.shr(b) are one and the same from an evaluation standpoint, they are different when it comes to type inference.
  • ShrAssign
    The right shift assignment operator >>=.
  • StorageClearable
  • StorageMapper
  • StorageTokenWrapper
  • Sub
    The subtraction operator -.
  • SubAssign
    The subtraction assignment operator -=.
  • TopDecode
    Trait that allows zero-copy read of values from an underlying API in big endian format.
  • TopEncode
  • TxAsyncCallCallback
  • TxCodeSource
  • TxCodeSourceSpecified
  • TxCodeValue
  • TxData
    Marks the data field of a transaction in Tx.
  • TxDataFunctionCall
  • TxEgldValue
  • TxEmptyResultHandler
    Indicates that given result handler is empty, i.e. doesn’t cause any side effects and returns nothing.
  • TxEnv
  • TxEnvMockDeployAddress
  • TxEnvWithTxHash
  • TxFrom
    Marks the sender of any transaction.
  • TxFromSourceValue
  • TxFromSpecified
    Marks the non-empty sender of a transaction.
  • TxGas
  • TxGasValue
  • TxNoPayment
    Marker trait that indicates that payment field contains no payment.
  • TxPayment
    Describes a payment that is part of a transaction.
  • TxPaymentEgldOnly
    Marks a payment object that only contains EGLD or nothing at all.
  • TxPaymentMultiEsdt
    Indicates that a payment object contains a multi-ESDT payment.
  • TxPromisesCallback
  • TxProxyTrait
    Defines a proxy object for a smart contract.
  • TxResultHandler
    Marks a general result handler, to be used in the transaction unified syntax.
  • TxTo
    Marks the recipient of any transaction.
  • TxToSpecified
    Marks the non-empty recipient of a transaction.
  • TypeAbi
    Implemented for all types that can end up in the ABI:
  • VMApi

Functions§

Type Aliases§