Alexey
Alexey
I like your ideas. The way we are mocking externs right now seems not very nice, to be honest. `pwasm-std` could provide the real context with external calls and we...
Better to keep contract Endpoint and Client generation using trait, but I like idea of context..
> it's easy, i can declare trait in one crate and other crate will just import this trait and implement it for it's own structures, with abi already defined as...
Like so https://play.rust-lang.org/?gist=6570adb28cbd3bb1c139e08389a6a12b&version=stable
@pepyakin yeap, the context gives us this flexibility. In the `_call` user could use `RealContext` with externs. In tests he could mock it.
> why ctor if i may ask? unless one comes from C# it will cause confusion. confusion leads to bugs. > why not constructor? it's unmistakeable! Name `ctor` comes from...
We have a current limitation with a "context" approach: currently we cant set that context on Client, cause in Client we directly use ext::call https://github.com/paritytech/pwasm-token-example/blob/master/src/token.rs#L49
seems so
makes sense
hm.. But from another point of view, Client and Endpoint have some good symmetry between..