Make CallableTransform and CallableInverse aliases of Base.Fix1
#122
Conversation
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
|
This makes sense. I assume that I should have merged this one before #123, would you mind resolving the conflicts? (Since this is my bad, if you have no time I will do it myself). |
|
OK, I fixed the merged conflicts 🙂 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I assume
CallableTransformandCallableInversepredate the use ofBase.Fix1etc. in the ecosystem. I think one could unify both paths of construction,transform(t)andBase.Fix1(transform, t)etc., and just makeCallableTransformandCallableInversespecial aliases ofBase.Fix1.Alternatively, one could remove these names completely, given that users have already been instructed to use
transform(t)andinverse(t).