NonBlockingFileIO has no async APIs

[adam-fowler]

It appears that the best option for file access is still NonBlockingFileIO. Currently to use NonBlockingFileIO in a Swift concurrency context you are required to use the EventLoop based API and EventLoopFuture.get. This is unsatisfactory because

1. You need an EventLoop to call any of the functions
2. Waiting on a process running on the NIOThreadPool requires two hops: one to the EventLoop and then one to your async task.

Are there any plans to produce async NonBlockingFileIO APIs?

[Lukasa]

We certainly plan to produce a solution in this area. However, in our ideal world this wouldn't be NIO-based at all, as the solution should be more general purpose than that.

[adam-fowler]

Would you be adverse to me producing a temporary solution that still uses NIOThreadPool but skips the EventLoopPromise and uses a Continuation instead?

This is basically the last barrier to removing EventLoops from Soto.

[Lukasa]

I'd be happy for you to do that work.

[JawadHF]

We certainly plan to produce a solution in this area. However, in our ideal world this wouldn't be NIO-based at all, as the solution should be more general purpose than that.

Just to understand, would that be something like Swift System ?

[Lukasa]

Swift System may be a little too low-level for that.