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 (type-safe-avl-1.0.0.1-r1) |
2022-08-14T21:45:51Z |
nico |
0f6aebe94ff8fca51a44becd2fd19f585e182868476ed13ff74a1fcfceae8a75
|
|
Changed description
from Several implementations of binary search trees (BST) and balanced binary search trees (AVL).
Verify at compile time if the operations over BST/AVL trees preserves the order of the keys
and the balance in the heights.
For both of them there's one unsafe implementation and three type-safe implementations.
The last ones differ one how the structural invariants are handled at the type level.
to Several implementations of type-safe binary search trees (BST) and balanced binary search trees (AVL).
These differ on how the structural invariants are implemented at the type level.
Each of them have their own advantages and disadvantages.
This library shows different ways of implementing invariants at the type level,
each of them providing different features, all of them enforced at compile time:
- Data invariant verification: assert at compile time if any given tree is BST/AVL.
- Program certification: verify at compile time if the implementation of the operations
over BST/AVL trees preserves the order of the keys and the balance in the heights.
- Type-safe data constructors: implementation of tree constructors that throw an error at compile time
if the tree being constructed is not BST/AVL.
|
-r0 (type-safe-avl-1.0.0.1-r0) |
2022-05-31T02:19:43Z |
nico |
a07e1c99bcbf2d7828b30e20d83dedf814f80d2c7fef45f408be1b716342148e
|
|
|