Simplify class, instance and type hierarchy around RingMap #62
Labels
No labels
ActivityPub
advanced features
basic functionality
bug
DHT
evaluation
refactoring
security
test case
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: schmittlauch/Hash2Pub#62
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
While refactoring RingMap, several language extensions had to be enabled without thoroughly considering their effects.
This leads to ugly code requirements such as enabling FlexibleContexts and having to explicitly state type hints like the ones introduced in #63.
The essence of the abstract RingMap type and its functions is being a map that stores elements according to a bounded (modular) and ordered key. This key can be extracted from these elements.