Open TerrorJack opened 2 years ago
This would be nice to have IMHO. It doesn't seem like there is an obvious way to pass the id of the actual and expected signature back to the wasmtime runtime. The trap is raised using a hardware trap instruction like ud2. This doesn't allow any arguments. Using a call instead would be possible though I suspect it will cause a perf regression, but I will leave it to others to judge as I am not familiar with this part of the code.
Feature
Currently, when a
call_indirect
opcode is executed with mismatching types,wasmtime
would display something like:It would be nice to have enriched error message that displays the expected/actual type signatures here, this will help debugging a lot.