I am not sure if this is a bug, but I found it unexpected: currently, when decodeTupleElems does not consume all the input then it returns only the tuple elements it managed to read, instead of failing.
This pull request changes that behaviour so that it fails instead.
I am not sure if this is a bug, but I found it unexpected: currently, when
decodeTupleElems
does not consume all the input then it returns only the tuple elements it managed to read, instead of failing.This pull request changes that behaviour so that it fails instead.