Skip to content

Add blog post on pipes. #222

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Add blog post on pipes. #222

wants to merge 3 commits into from

Conversation

Crell
Copy link
Contributor

@Crell Crell commented Jun 19, 2025

At Roman's request... This is equal parts RFC summary and background history.

I left out the divisive question of going with Elixir-style pipes, mostly for length. If folks feel it would add to the story I can include that, but I fear it may detract from the rah-rah aspect that I am trying to go for here.

I've put the date a few days out to allow for editing time, but of course re-date it as appropriate.

Copy link
Contributor

github-actions bot commented Jun 19, 2025

@github-actions github-actions bot temporarily deployed to pull request June 19, 2025 04:19 Inactive
@github-actions github-actions bot temporarily deployed to pull request June 19, 2025 18:14 Inactive
Which... gives us mostly the same thing as the long-discussed scalar methods! Only pipes are more flexible as you can use any function on the right-side, not just those that have been blessed by the language designers as methods.

At this point, pipe comes very close to being "extension functions", a feature of Kotlin and C# that allows writing functions that look like methods on an object, but are actually just stand-alone functions. It's spelled a bit differently (`|` instead of `-`), but it's 75% of the way there, for free.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be nice to add a subheader here if possible. Wdyt?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Eh, any one of these is somewhat arbitrary. They're an increasing scale of cool implications. I'd say put a 3rd level header on all of them, or on none of them. I lean none, but can do either.

@Crell
Copy link
Contributor Author

Crell commented Jul 3, 2025

Assorted updates made. I didn't mess with the date yet; I figure Roman can do that once whenever it's ready to go live.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants