• 0 Posts
  • 11 Comments
Joined 3 years ago
cake
Cake day: April 3rd, 2024

help-circle


  • When people say “async is viral” in Rust, they mean that once you make one function async, that change tends to ripple through the rest of your code. Any function that calls it usually has to become async as well so it can await the result. In turn, the callers of those functions often need to become async too.

    This propagation can continue all the way up the call stack until you reach your application’s entry point. The main exception is when you introduce an explicit synchronous-to-asynchronous boundary, such as by using block_on, which drives the future to completion without requiring the caller itself to be async.









  • Apple deployed a library I wrote to every mac on the world, and additionally bundles it with Xcode.

    Apple users reported some bugs, that‘s how I found out.

    I never heard a word from them. No patches, no bug reports, nothing, they didn’t even bother to refresh the bundled version.

    I think in the meantime they removed it from macOS but still bundle it with Xcode.

    I mean, I didn’t any money, but some appreciation would’ve been nice, and a version refresh…

    If you are curious: it is this library: https://github.com/ckruse/CFPropertyList

    Edit: appreciation as in: a mail with a notice that they did so.