Metadata revisions for ki-0.1.0.1
Package maintainers and Hackage trustees are allowed to edit certain bits
of package metadata after a release, without uploading a new tarball.
Note that the tarball itself is never changed, just the metadata that is
stored separately. For more information about metadata revisions, please
refer to the
Hackage Metadata Revisions FAQ.
No. |
Time |
User |
SHA256 |
-r1 (ki-0.1.0.1-r1) |
2020-12-01T01:40:55Z |
mitchellwrosen |
1767d81f2b3ea31c93ec04276a98bb06636be1dbba8d895b3393099b9427460e
|
|
Changed description
from A lightweight, structured-concurrency library.
This package comes in two variants:
* "Ki" exposes the most stripped-down variant; start here.
* "Ki.Implicit" extends "Ki" with an implicit context that's used to
propagate soft cancellation signals.
Using this variant comes at a cost:
* You must manually add constraints to propagate the implicit context to
where it's needed.
* To remain warning-free, you must delete the implicit context constraints
where they are no longer needed.
If you don't need soft-cancellation, there is no benefit to using this
variant, and you should stick with "Ki".
Because you'll only ever need one variant at a time, I recommend using a
<https://www.haskell.org/cabal/users-guide/developing-packages.html#pkg-field-mixins mixin stanza>
to rename one module to @Ki@ while hiding the others. This also simplifies the
process of upgrading from "Ki.Implicit" to "Ki" if necessary.
@
mixins: ki (Ki.Implicit as Ki)
@
to A lightweight, structured-concurrency library.
This package comes in two variants:
* "Ki" exposes the most stripped-down variant; start here.
* "Ki.Implicit" extends "Ki" with an implicit context that's used to
propagate soft cancellation signals.
Using this variant comes at a cost:
* You must manually add constraints to propagate the implicit context to
where it's needed.
* To remain warning-free, you must delete the implicit context constraints
where they are no longer needed.
If you don't need soft-cancellation, there is no benefit to using this
variant, and you should stick with "Ki".
Because you'll only ever need one variant at a time, I recommend using a
<https://www.haskell.org/cabal/users-guide/developing-packages.html#pkg-field-mixins mixin stanza>
to rename one module to @Ki@ while hiding the others. This also simplifies the
process of upgrading from "Ki.Implicit" to "Ki" if necessary.
@
mixins: ki (Ki.Implicit as Ki)
@
|
-r0 (ki-0.1.0.1-r0) |
2020-12-01T01:35:38Z |
mitchellwrosen |
0ecc7909557d1f339a8a29f044f357c483a531d5d649b613c9be9aeb50bd040b
|
|
|