MusicalNinjaDad

@barneygale - is there anything I can do to support with this? Should I rebase and reintegrate with all the work you've done on the ABCs?

Would you accept a simple documentation change to clarify this? The approach makes sense but isn't obvious - it's easy to assume that checking for a FormatError is sufficient to...

After documenting the situation, I got puzzled as to why a raw `io.EOF` was returned, when `os.Open` usually returns a `PathError`. A quick debug showed that the issue was actually...

Taking this into the debug/elf code removes the complexity from every single user of the library and puts it in one place where it can be done correctly & consistently....

I'll stick to the concrete usage that led to me noticing this and other use cases from the same codebase, rather than attempting to think of a long list of...

@ianlancetaylor - I guess I should close this and the associated PRs. A clear "not interested in fixing error handling" up front would have been courteous and saved me spending...

I clearly misinterpreted the recent communication. Thank you for the clarification and hope you enjoyed your Thanksgiving. I'm happy to reopen this and leave the ball in your court. Please...

I'd agree that just changing `io.EOF` to `io.ErrUnexpectedEOF` would probably not be worth it e.g.: ```go n, err := r.ReadAt(ident[0:], 0) if err != nil { if err == io.EOF...