Add support for multi-value proposal (#861)

Use the `--enable-multi-value` flag to enable.

A lot of code already "worked" with multi-value, and just needed to
remove the restrictions. Most of the other changes are modifying the
callback APIs to be more general, e.g. taking more than 1 result type.

* Types are now stored as the negative values; this works nicely with
  the encoding of inline function types (used for block signatures),
  which are always positive values.
* Remove `BlockSignature` and use `BlockDeclaration` instead, which
  is just a typedef to `FuncSignature`. This allows for explicit or
  implicit type specifications on the block signatures.
* Allow for >1 "keep" values in the DropKeep interpreter instruction

1 files changed, 1 insertions, 1 deletions

diff --git a/test/parse/expr/bad-binary-one-expr.txt b/test/parse/expr/bad-binary-one-expr.txt
index 28258a73..b7944dfe 100644
--- a/test/parse/expr/bad-binary-one-expr.txt
+++ b/test/parse/expr/bad-binary-one-expr.txt
@@ -7,7 +7,7 @@
 out/test/parse/expr/bad-binary-one-expr.txt:5:4: error: type mismatch in i32.add, expected [i32, i32] but got [i32]
    i32.add))
    ^^^^^^^
-out/test/parse/expr/bad-binary-one-expr.txt:5:4: error: type mismatch in function, expected [] but got [i32, i32]
+out/test/parse/expr/bad-binary-one-expr.txt:5:4: error: type mismatch in function, expected [] but got [i32]
    i32.add))
    ^^^^^^^
 ;;; STDERR ;;)