News for hackers. Stuff that matters.

A comment on Making a Go program 70% faster with a one character change. Parent comment

Re:Making a Go program 70% faster with a one character change by robotresearcher on Monday November 14, 2022 @04:24PM (#33601336)
If you take the position that the semantics of read() are 'read data from this endless stream', then EOF is an error indicating that this model no longer applies.

Doesn't bother me at all.

[ Parent | on HN ]
Re:Making a Go program 70% faster with a one character change by account42 on Tuesday November 15, 2022 @04:42AM (#33607156)
Except in that model it would be fine to return an error as soon as soon as you know there is an EOF while in the real world you do want to read right up to the EOF because EOF is usually not an error condition but expected, even with streams of indeterminate length.
[ Parent | on HN ]
Re:Making a Go program 70% faster with a one character change by robotresearcher on Tuesday November 15, 2022 @11:30AM (#33611296)
The model is that you don’t know there’s an EOF until you’ve read the last byte.
[ Parent | on HN ]