Merged
Conversation
These operators (|!>) and (<!|) ideally should be called (!>) and (<!) but the problem is that (!>) is unary and it turns out it will be the most used of the 2, because it's in the direction of typical F# pipes.
wallymathieu
approved these changes
Feb 12, 2026
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
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.
These operators
(|!>)and(<!|)ideally should be called(!>)and(<!)but the problem is that(!>)is unary and it turns out it will be the most used of the 2, because it's in the direction of typical F# pipes.I think these operators are quite handy in real world code scenarios, when ignoring a value wrapped in a Task for example, then replacing it with another.