Simplify class, instance and type hierarchy around RingMap #62

Open
opened 2020-07-25 23:40:28 +02:00 by schmittlauch · 0 comments
Owner

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.

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.
schmittlauch added the
refactoring
label 2020-07-25 23:40:38 +02:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: schmittlauch/Hash2Pub#62
No description provided.