pink-web3 0.19.4

Ethereum JSON-RPC client for pink.
Documentation
//! Ethereum JSON-RPC client (Web3).

#![allow(
    clippy::type_complexity,
    clippy::wrong_self_convention,
    clippy::single_match,
    clippy::let_unit_value,
    clippy::match_wild_err_arm
)]
#![warn(missing_docs)]
// select! in WS transport
#![recursion_limit = "256"]
#![cfg_attr(not(any(feature = "std", feature = "test", test)), no_std)]

#[cfg(test)]
use jsonrpc_core as rpc;

#[macro_use]
extern crate alloc;

pub use ethabi;
// it needs to be before other modules
// otherwise the macro for tests is not available.
#[macro_use]
pub mod helpers;

mod prelude {
    pub(crate) use alloc::borrow::ToOwned as _;
    pub(crate) use alloc::string::String;
    pub(crate) use alloc::string::ToString as _;
    pub(crate) use alloc::vec;
    pub(crate) use alloc::vec::Vec;
    #[cfg(not(any(feature = "std", feature = "test", test)))]
    pub(crate) use core as std;
}

use prelude::*;

/// Re-export of the `futures` crate.
#[macro_use]
pub extern crate futures;

pub mod api;
pub mod confirm;
pub mod contract;
pub mod error;
pub mod keys;
pub mod signing;
pub mod transports;
pub mod types;

pub use crate::{
    api::{Accounts, Eth, Web3},
    error::{Error, Result},
};

/// Assigned RequestId
pub type RequestId = usize;

type Value<'a> = &'a dyn erased_serde::Serialize;

// TODO [ToDr] The transport most likely don't need to be thread-safe.
// (though it has to be Send)
/// Transport implementation
pub trait Transport: Clone {
    /// The type of future this transport returns when a call is made.
    type Out: core::future::Future<Output = Result<Vec<u8>>>;

    /// Execute remote method with given parameters.
    fn execute(&self, method: &'static str, params: Vec<Value>) -> Self::Out;
}

impl<T: Transport> Transport for &T {
    type Out = T::Out;

    fn execute(&self, method: &'static str, params: Vec<Value>) -> Self::Out {
        (*self).execute(method, params)
    }
}