Closed AurevoirXavier closed 5 years ago
According to stackoverflow, seems the only solution is updating the dependency?
@AurevoirXavier: I think you are right and this must be the reason. Good catch!
I remember someone updating this recently, are did you have this issue on master?
@kianenigma Just with substrate-node-new xxx xxx
, current version is rev = a857f4f88722419a6781e8810028089112380466
.
I will try with master.
There is no compatibility between 0.1.1 and 0.7.0, but actually I only published 0.7.0 over the weekend so someone updated pretty fast. Actually transitioning form 0.1.1 to 0.7 will disrupt any testnets.
We're done with the audit and 0.7.0 has the final wire formal, so I'll love to yank 0.1.* shortly. I think yanking would not break any code currently using 0.1.1 but might make it impossible to register new crates as using 0.1.1.
Branch v1.0 also has this problem.
I wrote an erc20_demo which similar to substrate-erc20 and it works good.
I change
pub trait Trait: system::Trait {}
topub trait Trait: assets::Trait {}
, and add a functionf()
to do something withassets
:After that I got a compiling error:
Here's cargo tree: