-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: update Operators overview #6819
docs: update Operators overview #6819
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@EnricoPicci, thanks for your contribution. Changes LGTM, but there's a conflict that needs to be resolved.
@jakovljevic-mladen Thanks for your reply. To be honest I do not know how to resolve this conflict. Can you guide me? Thanks |
Introduce the concept that what we normally call "operators", such as `map` or `filter`, are Pipeable Operator Factory functions which, when called, return a "real" Pipeable Operator.
@EnricoPicci, it's a bit hard 🙂 I can do it for you? |
@jakovljevic-mladen if you can do it, please do it. Thanks a lot. |
07726c0
to
d5dc306
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks and sorry for waiting this long.
Thank you and have a nice day |
Introduce the concept that what we normally call "operators", such as `map` or `filter`, are Pipeable Operator Factory functions which, when called, return a "real" Pipeable Operator. (cherry picked from commit a292214)
Introduce the concept that what we normally call "operators", such as
map
or
filter
, are Pipeable Operator Factory functions which, when called,return a "real" Pipeable Operator.
Description:
BREAKING CHANGE:
Related issue (if exists):