Alex Beregszaszi

@chfast can you clarify which convention you referred to or which one you prefer?

> What about returning a carry where necessary, e.g. add256? We kind of agreed to have another set of methods with carry.

For case 2) it is a question of compatibility - does it want to be compatible with the current _Contract ABI_ (and therefore `web3.js` and client apps). For the other...

Can WASM code export multiple methods? Each of the ABI signatures could be an exported method and this removes the need of writing a dispatcher as we have in current...

So with https://github.com/WebAssembly/design/blob/master/DynamicLinking.md we could make this a reality. Basically, we could define that an import where the module is an Ethereum address, will load the code from that address,...

The problem is not when importing library:main into the contract, but it enabled the library to be executed as a contract as not only loaded as a module. I don't...

If we define a contract as an eWASM module, which has an export called `main` and no other exports; and we define a library as an eWASM module, which doesn't...

A new idea: offer deploy time linking. [Following the above semantics](https://github.com/ewasm/design/issues/17#issuecomment-242222472) we do run into a problem: should this dynamic linking be done at runtime? If so, how do we...

Relocations specification: https://github.com/webassembly/tool-conventions/blob/master/Linking.md It also touches on the producers section.

For both ctz/clz we have decided to take a fairly naive implementation for calculating the cost to suit all VM implementations.