Changelog of @hackage/ki 1.0.1.2

[1.0.1.2] - July 15, 2024

Bugfix #33: A scope could erroneously fail to propagate an exception to one of its children.
Refactor: depend on (rather than inline) int-supply package.

Change #25: Attempting to fork a thread in a closing scope now acts as if it were a child being terminated due to the scope closing. Previously, attempting to fork a thread in a closing scope would throw a runtime exception like error "ki: scope closed".
Change #27: Calling awaitAll on a closed scope now returns () instead of blocking forever.

Bugfix #20: previously, a child thread could deadlock when attempting to propagate an exception to its parent.

Breaking: Remove Context type, Ki.Implicit module, and the ability to soft-cancel a Scope.
Breaking: Remove Duration type and its associated API, including waitFor and awaitFor.
Breaking: Remove Ki.Internal module.
Breaking: Generalize async to forkTry.
Breaking: Generalize forkWithUnmask to forkWith.
Breaking: Make fork_ take an IO Void rather than an IO ().
Breaking: Make fork create an unmasked thread, rather than inherit the parent's masking state.
Breaking: Rename waitSTM to awaitAll (replacing the old wait in IO).
Change: Make scoped kill threads in the order they were created.
Bugfix: Fix small memory leak related to closing a scope.
Bugfix: Fix subtle bug related to GHC's treatment of deadlocked threads.
Bugfix: make async (now forkTry) propagate async exceptions.
Bugfix: make scoped safe to run with asynchronous exceptions masked.
Bugfix: propagate exceptions to creator of scope, not creator of thread
Performance: Use atomic fetch-and-add rather than a TVar to track internal child thread ids.

Misc: Replace AtomicCounter with Int to drop the atomic-primops dependency.
Bounds: Lower cabal-version from 3.0 to 2.2 because stack cannot parse 3.0.