Skip to content
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

Find a champion to get this proposal to stage 0 #33

Closed
TehShrike opened this issue Mar 17, 2016 · 28 comments
Closed

Find a champion to get this proposal to stage 0 #33

TehShrike opened this issue Mar 17, 2016 · 28 comments
Labels

Comments

@TehShrike
Copy link
Collaborator

There seems to be consensus on the question of operator precedence, and I really want to see this pull request merged so that I can start using the operator!

However, on that pull request it looks like the operator needs a "TC39 champion". I'm not up on the protocol, so I'm opening this issue so that other people who have a better idea what's up can list the next steps for finding a champion and getting this proposal brought up at whatever meetings are appropriate.

@thelinuxlich
Copy link

C'mon, let's make this happen!

@TehShrike
Copy link
Collaborator Author

Can anyone paste a link to reading material on how TC39 championship works?

@stormpat
Copy link

stormpat commented May 3, 2016

@TehShrike

Heres some links:

https://tc39.github.io/process-document/
https://github.com/orgs/tc39/people <-- "champions" ?
http://tc39wiki.calculist.org/about/harmony/
https://github.com/tc39/ecma262/blob/master/CONTRIBUTING.md

If you have a new proposal you want to get into the language, you first need a TC39 champion. Head to *es-discuss to find one. If you already have a TC39 champion, send a pull request to add a link to your proposal to the Current Proposals list or the stage zero list.

@jasmith79
Copy link

Here's the es-discuss thread (warning, last message was 5 mo ago):
https://esdiscuss.org/topic/the-pipeline-operator-making-multiple-function-calls-look-great

@appsforartists
Copy link

It'll be easier to find a champion if you have spec text. Has anyone tried writing some?

@babakness
Copy link

Keep the dream alive!

@kentcdodds
Copy link
Member

As a PayPal delegate for TC39, I'd like to champion this proposal. I've never done that before though so I'll probably need help from folks :) I'll be in touch! 🎉

@bterlson
Copy link
Member

bterlson commented Jun 8, 2017

@rbuckton and I are championing a proposal similar to this with Ron Buckton. Happy to work together! Sorry I haven't been active on this repo - there's a lot of moving pieces I wanted to figure out first. The gist of what I will propose is the |> syntax that composes with syntax for partial application (foo(10, ?)) and possibly a smaller form of the bind operator for this-based pipelining.

The dream is alive!

@appsforartists
Copy link

@bterlson, which repo will you be using?

@bterlson
Copy link
Member

bterlson commented Jun 8, 2017

@appsforartists an official TC39 one, not sure of more yet though.

@jamen
Copy link

jamen commented Jun 15, 2017

@bterlson That sounds great. Please be sure to notify here, because I actually like what you proposed there a bit more (reminds me more of Elixir). 😄

@mikehaas763
Copy link

@bterlson awesome 👍

@hzoo
Copy link

hzoo commented Jul 21, 2017

Looks like this will possibly be presented at next week's meeting: https://github.com/tc39/agendas/blob/master/2017/07.md

@littledan
Copy link
Member

littledan commented Jul 21, 2017

I put myself up as backup champion. If @bterlson doesn't end up presenting it as he mentioned above, I will, to get things moving. But, to be clear, I'm more than happy to have @bterlson and @rbuckton taking this on.

@bterlson
Copy link
Member

@gilbert can you transfer this repository to TC39? First transfer to me and then I can transfer to the TC39 organization.

@bterlson
Copy link
Member

Also interesting to people in this thread: https://github.com/rbuckton/proposal-partial-application

@gilbert
Copy link
Collaborator

gilbert commented Jul 21, 2017

@bterlson Transfer requested.

@babakness
Copy link

babakness commented Jul 21, 2017

This is awesome... I have to admit that looking at it I wonder... so if we have syntax sugar for pipe, why not compose too? So a <| operator as well as the |> operator. It just feels more complete with both.

Compose is more natural when thinking about components, because the outer contains the inner, i.e.:

outerComponent <| middleComponent <| innerComponent

@gilbert
Copy link
Collaborator

gilbert commented Jul 21, 2017

@babakness I think it's best to discuss that in a separate issue.

@bterlson
Copy link
Member

@babakness @rbuckton is thinking about exactly this, perhaps he can provide more details. I agree with a separate issue though, good future extension.

@bterlson
Copy link
Member

@gilbert I'm very very sorry, I missed the transfer request window :( Can you send again? I'll be available for the next ~7 hours to accept it.

@gilbert
Copy link
Collaborator

gilbert commented Jul 24, 2017

@bterlson No problem, sent again.

@bterlson
Copy link
Member

@gilbert done :)

@Alexsey
Copy link

Alexsey commented Aug 4, 2017

Is there anything else need to be done before adding this to https://github.com/tc39/proposals/blob/master/stage-0-proposals.md ?

@littledan
Copy link
Member

It has to be discussed at the meeting. I put it on the agenda for the last meeting, but we ran out of time. We'll see if we can discuss it next time.

@Alexsey
Copy link

Alexsey commented Oct 2, 2017

It finally gets to the proposals repo, and not just on stage 0, but directly to stage 1! Thank you @bterlson and other champions who take this proposal from making it happened! I think issue may be closed now

@TehShrike
Copy link
Collaborator Author

👏 🎉 👏

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests