Open
Conversation
smunix
force-pushed
the
fix.no-TypeCompose
branch
4 times, most recently
from
3da63f5 to
f6542a3
Compare
and use Data.Functor.Compose from base. * use hpack to generate cabal * build with Nix * bump stack to use lts-20.4 * bump version to 0.5.0.2
smunix
force-pushed
the
fix.no-TypeCompose
branch
from
f6542a3 to
7546490
Compare
Author
|
Integration with |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
TypeCompose being depecrated by Conal E (see conal/TypeCompose#12), this PR is effectively removing it from spatial-math.
Control.Composeusage has been replaced byData.Functor.Composefound inbase.Here's the full list of noticeable changes in this PR:
and use Data.Functor.Compose
from base.