How to use generic structs in the Parity Substrate custom runtime?

3
votes

I want to create a data type using Struct inside a Parity Substrate custom runtime. The data type is intended to be generic so that I can use it over different types.

I am trying the following, but it's not compiling. The compiler complains about sub-types not found for T.

pub struct CustomDataType<T> {
    data: Vec<u8>,
    balance: T::Balance,
    owner: T::AccountId,
}

I should be able to compile a generic struct.

2
rustsubstrate
The compiler will not know where the associated types Balance and AccountId came from, unless you apply a trait bound on T that provides them. Next time, please see what makes a proper minimal reproducible example, and don't forget to include relevant crates and modules. - E_net4 the curator
Please review how to create a minimal reproducible example and then edit your question to include it. We cannot tell what crates, types, traits, fields, etc. are present in the code. Try to produce something that reproduces your error on the Rust Playground or you can reproduce it in a brand new Cargo project. There are Rust-specific MCVE tips as well. - Shepmaster

2 Answers

6
votes

Unfortunately, the answer that Sven Marnach gives does not work in the context of Parity Substrate. There are additional derive macros which are used on top of the struct which cause issues when going down the "intuitive" path.

In this case, you should pass the traits needed directly into your custom type and create new generics for the context of the struct.

Something like this:

use srml_support::{StorageMap, dispatch::Result};

pub trait Trait: balances::Trait {}

#[derive(Encode, Decode, Default)]
pub struct CustomDataType <Balance, Account> {
    data: Vec<u8>,
    balance: Balance,
    owner: Account,
}

decl_module! {
    // ... removed for brevity
}

decl_storage! {
    trait Store for Module<T: Trait> as RuntimeExampleStorage {
        Value get(value): CustomDataType<T::Balance, T::AccountId>;
    }
}

We just created a doc for this exact scenario which I hope helps.

3
votes

It looks like T::Balance and T::AcountId are assoicated types of some trait, so they can be only used if that trait, say MyTrait, is implemented for T. You can tell the compiler that T implements MyTrait by adding a trait bound:

pub struct CustomDataType<T: MyTrait> {
    data: Vec<u8>,
    balance: T::Balance,
    owner: T::AccountId,
}

In general, you can only assume properties, methods and asscociated types of a generic type if the type is restricted by appropriate type bounds. (The only exception is that type parameters are assumed to be sized by default, so you can make this assumption without an explicit bound.)