Descriptive call_indirect trap error messages #178
Description
In debugging some wasm files with some folks today one thing we ran across was that call_indirect was having a mismatched function signature, but unfortunately all we got out of wasmtime was that a trap happened. It would have been more useful if the error message (perhaps optionally via the -d flag?) had included information about what the expected signature was and what the found signature was. Ideally we'd go back to offsets into the original wasm file as well, but that's fine being a bit of a reach!