Handle.Call() does not return error when a command fails

[ArnoSen]

As described in the comments for Handle.Call(), it only errors out when
error if handle is invalid, or problem encountered during sending or receiveing. .

However, when a command fails because e.g. a syntax error or an object that is not there, Handle.Call() will not error out. After Handle.Call() has been called, it is not possible anymore to get the error related to a failed command.

I see a couple of possible solutions:
1 Handle.Call() will return an error, next to communication errors, if any of the commands failed.
2 Handle.Call() will return an array of errors so the developer can find out which command failed more easily.

Changing the Handle.Call can break the API, so I would suggest to implement new methods:

• CallWithCommandError() (error): this will return an error when a command failed.
• CallWithCommandErrors(error, []error): this will return the current error object together with a slice of errors one for each command.

What do you think?

[ArnoSen]

Probably this was caused by something in my code. I am closing this issue