v4.0

[kazu-yamamoto]

We introduce breaking changes:

• Specifying Strict and StrictData to avoid space leak (Using strict language extension #412)
• Integrating with the new Windows IO manager (Integrate with the new Windows IO manager #364)
• Correcting socket type on Windows (Socket type is incorrect on Windows #426)
• Correcting address argument in recvfrom() (Incorrect handling of address argument in recvfrom() #539)
• Supporting GHC 9.x only

@Mistuke It's time!

[coot]

@kazu-yamamoto do you want us to help with it? I won't have time right now, but I might get some help from our partners (Galois).

[kazu-yamamoto]

@coot I'd love to help you. But as talked in #559, the baton was passed to @Mistuke now.
When he show me the first example, I can hack the entire package.

[Mistuke]

Sorry for the quiet, I'm just stretched very thin at work. I have a nice 20h flight this week and will do so then! You should get something by Friday!

…

Sent from my Mobile

On Tue, Jul 4, 2023, 03:52 Kazu Yamamoto ***@***.***> wrote: @coot <https://github.com/coot> I'd love to help you. But as talked in #559 <#559>, the baton was passed to @Mistuke <https://github.com/Mistuke> now. When he show me the first example, I can hack the entire package. — Reply to this email directly, view it on GitHub <#557 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAI7OKLKPUF47H35BETJWS3XOOAQFANCNFSM6AAAAAAYTJ3Z3Q> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[kazu-yamamoto]

Supporting WinIO is delayed.
I would like to set the target version to v4.0.
I will use v3.2 for other purposes.

[TravisWhitaker]

I'm curious about whether or not the public interface needs to change in order to support WinIO. My understanding is that IOPort is roughly analogous to what's achieved with threadWait* in the current implementation: request the IO and the block the Haskell thread until it's completed.

In general it seems desirable to maintain the pattern that GHC users currently employ: forkIO as many threads as you need, let them block when they need to, and let the IO manager handle the rest. The absence of Rust/Swift/etc. asynchronous callback style APIs is one of big advantages of Haskell's concurrency model.

[kazu-yamamoto]

Good point. We don't bump major version if not necessary.

[TravisWhitaker]

Well, whether or not to bump the major version is one question, and whether or not to move to a callback-based async style API in this package is another entirely.

[Mistuke]

To get Winio to work doesn't need an API change. To get the most out of it will eventually. If RIO is to ever be implemented the DMA interface needs to be exposed to users. For instance a single haskell thread can easily handle multiple io requests.

[TravisWhitaker]

What would it look like for a single Haskell green thread to handle multiple concurrent requests?