You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I drafted up an initial version of the explainer for the F# Pipeline Operator. It's built on the current implementation's explainer, so there's some overlap, but I tried to address some of the discussions we've had since then, like importable methods, as well as explain how p |> await works.
I also opened a pull request into the repository to officially include #104 as part of the operator. That said, writing parentheses around assignment, even in the explainer, was really annoying, so I'd love to make it work without requiring parentheses there. If that isn't feasible, I'm not sure we should do it. We need to make a decision before I can implement the babel plugin, or we need to implement another flag to test both.
Otherwise, interested in questions, comments, suggestions. I've got a few other things I'm going to add marked in issues, but I'm ready to hear feedback.
The text was updated successfully, but these errors were encountered:
I drafted up an initial version of the explainer for the F# Pipeline Operator. It's built on the current implementation's explainer, so there's some overlap, but I tried to address some of the discussions we've had since then, like importable methods, as well as explain how
p |> await
works.I also opened a pull request into the repository to officially include #104 as part of the operator. That said, writing parentheses around assignment, even in the explainer, was really annoying, so I'd love to make it work without requiring parentheses there. If that isn't feasible, I'm not sure we should do it. We need to make a decision before I can implement the babel plugin, or we need to implement another flag to test both.
Otherwise, interested in questions, comments, suggestions. I've got a few other things I'm going to add marked in issues, but I'm ready to hear feedback.
The text was updated successfully, but these errors were encountered: