Created isLabel and HasLabel classes #643
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is for issue #629.
In this PR, the classes
IsLabel
andHasLabel
are created, addressing theisLabel
section under in #567.@JacquesCarette @szymczdm Is it not desirable to have classes defined anywhere other than the Classes.hs file? I had to move the definitions into the Label.hs file due to cyclic imports (i.e. data type
Label
needs aUID
, which meansLabel
is an instance ofHasUID
, which needs to be imported from Classes.hs; this meant that defining the new classes in Classes.hs wouldn't work because in order to lens to aLabel
, the data typeLabel
needs to be recognized in that file (i.e. Label.hs needs to be imported into Classes.hs)).