The code in transport is using blocking to IO, making the claim that the library is using Std.Async too strong.
Indeed, the libuv loop is blocked at reading/writing data, making the code actually completely synchronous.
For real Async, the code should be Async al the way down to the public API. This would allow operation chaining to stay async.
I asume the LLM was not guided properly to generate this code.
The code in transport is using blocking to IO, making the claim that the library is using Std.Async too strong.
Indeed, the libuv loop is blocked at reading/writing data, making the code actually completely synchronous.
For real Async, the code should be Async al the way down to the public API. This would allow operation chaining to stay async.
I asume the LLM was not guided properly to generate this code.