Nikolay Volf

There is no need to support json in no-std, because json is generated on compile time only and json serialization/deserialization never makes it to the wasm binary

it's actually out of scope of `pwasm-std`, but worth discussion anyway i believe there could be multiple implementations of storage in different crates based on the same low-level-api, user will...

@snd https://github.com/paritytech/parity/blob/master/ethcore/wasm/src/runtime.rs#L180 it uses `Ext` `Ext` is implemented for `Externalities`: https://github.com/paritytech/parity/blob/master/ethcore/src/externalities.rs

Not necessary, but i don't see why not At least at the same repo

such approach has a lot of downsides - you can't implement multiple contracts with known interface (trait) this way - you can't split interface (trait) and it's implementation - you...

@snd yeah, downside with `Context` is pretty simple - you should always prefer implementation complexity over public api complexity. Currently pwasm-std api is pretty simple and consist only of functions,...

On the second thought, idea with context might be useful, if traits will not be generic over it. @fckt might come with proof-of-concept in this repo (it can be achieved...

Just wanted to note about gist is that better always require `&mut self` in the `Context`. Rust `&mut` is not only about mutability, but also about uniqueness, and `Context` should...

> ctor it has nothing to do with solidity actually, it's just me; i will rename it in abi reimplementation i'm working on now

@snd, it has little to do with context and tests, it's how runtime works parity has the same "externalities" (and with much more functions) for both evm and wasm https://github.com/paritytech/parity/blob/master/ethcore/src/externalities.rs