You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before filing a bug, please check whether it has been fixed since the
latest release. Search the issue tracker and check that you're running the
latest version of Go:
Run "go version" and compare against
http://golang.org/doc/devel/release.html If a newer version of Go exists,
install it and retry what you did to reproduce the problem.
Thanks.
What steps will reproduce the problem?
If possible, include a link to a program on play.golang.org.
1. http://play.golang.org/p/-4L5yBHnhX
What is the expected output?
1 EOF
What do you see instead?
1 <nil>
Which compiler are you using (5g, 6g, 8g, gccgo)?
6g
Which operating system are you using?
OSX
Which version are you using? (run 'go version')
go version go1.0.3
Please provide any additional information below.
The reason I believe the current output is incorrect is the docs on io.ReaderAt,
specifically (from http://golang.org/pkg/io/#ReaderAt)
" When ReadAt returns n < len(p), it returns a non-nil error explaining why more
bytes were not returned. In this respect, ReadAt is stricter than Read. "
The current source for io.go reduces the size of the underlying ReadAt to match the size
of the section. This means that EOF is never returned (except sometimes if the section
lines up with the end of the file).
The text was updated successfully, but these errors were encountered:
by sam@eversoft.co.nz:
The text was updated successfully, but these errors were encountered: