Nikolay Volf

@cyberbono3 fixed for the latest rust version

I see no use-cases for those opcodes, since wasm can hardly reason about its own code (because of wasm Harvard architecture), not everything is implementable in the same way as...

why closing? i think it might be better implementation then current ;)

It’s about any type array, not fixed bytes array

Hi, `pwasm-abi` does not support fallback, but nothing prevents you from handling input data bytes manually You just need to use [input function](https://paritytech.github.io/pwasm-ethereum/pwasm_ethereum/fn.input.html) to fetch those bytes and handle them...

But we would like to support fallback functions anyway for different use cases

Hi! No members ever get persisted or stored anywhere indeed This is also out of scope of `pwasm-abi` library :)

According to [this discussion](https://www.reddit.com/r/rust/comments/3696wt/checking_that_functions_are_constant_time_with/), it is probably out of reach for rust and llvm in general