Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(493)

Issue 7249045: code review 7249045: encoding/base64: fix test for ReadFull change (Closed)

Can't Edit
Can't Publish+Mail
Start Review
Created:
12 years, 5 months ago by rsc
Modified:
12 years, 5 months ago
Reviewers:
bradfitz
CC:
golang-dev
Visibility:
Public.

Description

encoding/base64: fix test for ReadFull change

Patch Set 1 #

Patch Set 2 : diff -r e7f267e20b7f https://code.google.com/p/go/ #

Patch Set 3 : diff -r e7f267e20b7f https://code.google.com/p/go/ #

Patch Set 4 : diff -r 3a9b191a06e1 https://code.google.com/p/go/ #

Unified diffs Side-by-side diffs Delta from patch set Stats (+1 line, -0 lines) Patch
M src/pkg/encoding/base64/base64_test.go View 1 1 chunk +1 line, -0 lines 0 comments Download

Messages

Total messages: 5
rsc
Hello golang-dev@googlegroups.com, I'd like you to review this change to https://code.google.com/p/go/
12 years, 5 months ago (2013-01-31 22:34:21 UTC) #1
rsc
*** Submitted as https://code.google.com/p/go/source/detail?r=8cbc63724b26 *** encoding/base64: fix test for ReadFull change R=golang-dev CC=golang-dev https://codereview.appspot.com/7249045
12 years, 5 months ago (2013-01-31 22:44:00 UTC) #2
bradfitz
I looked at this test code, ioutil.ReadAll, bytes.ReadFrom, and I'm not seeing why this was ...
12 years, 5 months ago (2013-01-31 22:47:35 UTC) #3
rsc
ReadAll is reading from the base64.decoder Read method. That method calls ReadAtLeast to read from ...
12 years, 5 months ago (2013-01-31 22:52:14 UTC) #4
bradfitz
12 years, 5 months ago (2013-01-31 23:07:44 UTC) #5
LGTM

Ah, I didn't read the Decoder.Read... I jumped right to reading
the faultInjectorReader's Read.  Makes sense.

On Thu, Jan 31, 2013 at 2:52 PM, Russ Cox <rsc@golang.org> wrote:

> ReadAll is reading from the base64.decoder Read method. That method calls
> ReadAtLeast to read from the faultInjectorReader. The one actual side
> effect of the ReadAtLeast/ReadFull change is that a read that returns
> enough data+error will have the error discarded, on the assumption that a
> future read will get the same error. The faultInjectorReader's Reads are
> satisfied by responses sent on the nextc channel. It needed a 0, err
> response for that additional Read.
>
> Russ
>
>
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b