Actually yes - it implies that if the read/write executes, then the read/write was successful.
In practice, in cases where a nil read/write could happen, a default "fall through" option on a select statement is used.
They could have made the original interface return a possible error for reading/writing, in line with regular go error handling, but opted instead to use more channel-based conventions.
In practice, in cases where a nil read/write could happen, a default "fall through" option on a select statement is used.
They could have made the original interface return a possible error for reading/writing, in line with regular go error handling, but opted instead to use more channel-based conventions.