subxt 0.50.0

Interact with Substrate based chains on the Polkadot Network
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
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47

use crate::backend::BlockRef;
use crate::config::{Config, HashFor, Hasher};

/// This represents either a block number or a reference
/// to a block, which is essentially a block hash.
pub enum BlockNumberOrRef<T: Config> {
    /// A block number.
    Number(u64),
    /// A block ref / hash.
    BlockRef(BlockRef<HashFor<T>>),
}

impl<T: Config> From<u32> for BlockNumberOrRef<T> {
    fn from(value: u32) -> Self {
        BlockNumberOrRef::Number(value.into())
    }
}

impl<T: Config> From<u64> for BlockNumberOrRef<T> {
    fn from(value: u64) -> Self {
        BlockNumberOrRef::Number(value)
    }
}

impl<T: Config> From<usize> for BlockNumberOrRef<T> {
    fn from(value: usize) -> Self {
        BlockNumberOrRef::Number(value as u64)
    }
}

impl<T: Config> From<BlockRef<HashFor<T>>> for BlockNumberOrRef<T> {
    fn from(block_ref: BlockRef<HashFor<T>>) -> Self {
        BlockNumberOrRef::BlockRef(block_ref)
    }
}

// Ideally we'd have `impl From<HashFor<T>> for BlockNumberOrRef<T>` but since our config
// could set _any_ hash type, this boils down to `impl From<H> for ..` which is too general.
// Thus, we target our current concrete hash type.
impl<T: Config> From<crate::config::substrate::H256> for BlockNumberOrRef<T>
where
    <T::Hasher as Hasher>::Hash: From<crate::config::substrate::H256>,
{
    fn from(hash: crate::config::substrate::H256) -> Self {
        BlockNumberOrRef::BlockRef(BlockRef::from_hash(hash.into()))
    }
}