Move isType
out of internal and make it a predicate named isSameType
#50
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.
The home stretch
As we come closer to feature lockdown it is time to start cleaning up, optimizing and removing all the duplication (mostly around type assertions).
This PR is the first step in that process. The old and crusty
isType
just would not live in the new world. So this updates that function to be able to compare types properly in one place. Also, as it is a better interface, it is time to expose it as a real predicate available to the public. So gets a new name and an introduction to the world.In addition to this move, and cutting over all dependent files, did a couple more 💄 bits:
both
toArrow
andStar
on the READMEpredicate
signatures on the READMEisBoolean
isInteger
isMonad
isSetoid
isTraverable