docs: Clarify that "ERROR" is a byte string

`string` can be ambiguous as `Tuple` layer supports both `byte string`
and unicode `string`.

Signed-off-by: Rajiv Ranganath <rajiv.ranganath@atihita.com>
This commit is contained in:
Rajiv Ranganath 2021-11-19 06:11:04 +05:30
parent 22e34bd6b9
commit ad56935216

View File

@ -117,8 +117,8 @@ should simulate it using an anonymous transaction. Remember that set and clear
operations must immediately commit (with appropriate retry behavior!).
Any error that bubbles out of these operations must be caught. In the event of
an error, you must push the packed tuple of the string `"ERROR"` and the error
code (as a string, not an integer).
an error, you must push the packed tuple of the byte string `"ERROR"` and the
error code (as a byte string, not an integer).
Some operations may allow you to push future values onto the stack. When popping
objects from the stack, the future MUST BE waited on and errors caught before