1. 104
  1.  

  2. 17

    On async I/O:

    This is a big deal. It means that Zig code can express concurrency, yet be reusable in both a blocking I/O and an evented I/O environment. There is no “async-std”. The Zig Standard Library supports both async and blocking I/O with the same codebase.

    Wow! Looking forward to watching this mature.

    1. 1

      Sounds exactly like GHC’s runtime, and is what makes writing IO heavy concurrent code in Haskell such a dream - just fork more threads and let the RTS handle scheduling them and waking them when data arrives.

    2. 13

      @andrewrk great work!

      Aside: Oof. Those release notes must take a long time to write up.

      1. 41

        two weeks of basically doing nothing else x_x

        1. 8

          Ha! Well, I certainly appreciate reading such nice release notes. Reading through it is like unwrapping a present!
          Er.. I mean present.? ;)

        2. 3

          But I bet it’s a good feeling when you release it and can point out all the stuff you’ve done

        3. 5

          Congratulations !

          I am impressed by the commitment and the number of contributors in this release : it looks like Zig is on a good path :)

          So far, it is a real pleasure to work with Zig and it allows me to learn new things every day.

          Besides, I am glad to see some stuff regarding TCP sockets : I hope to be able to show a very barebone HTTP client in the upcoming month :)

          1. 2

            With the new bootstrap tarball does this increase the chance of Zig supporting OpenBSD?

            1. 1

              nice! finally a tarball for my raspberry pi! :D