Hi everyone,
I was always under the impression that Go solely uses async I/O under the
hood so that when invoking a seemingly blocking call like os.File.Read the
underlying thread won't be blocked. Go scheduler will save the context of
current goroutine and schedule other goroutines to run on t
ot actually stored on the
disk, can I assume in this case there won't be any thread blocked?
On Friday, May 31, 2024 at 12:34:38 PM UTC-7 Ian Lance Taylor wrote:
> On Fri, May 31, 2024 at 12:09 PM Haoyang Fan wrote:
> >
> > I was always under the impression that Go solely