-
Notifications
You must be signed in to change notification settings - Fork 30
Is this proposal dead? #53
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
Comments
I found #44 has active discussion. |
Mostly this proposal is near dead. But I think it could revive to two separate proposals:
|
@hax I'm confused. How would method extraction work? You'd pull out a method from an object so that you can call it with a specific binding ? |
@zfrisch I believe the idea is to extract a method whose receiver remains bound to the object it's extracted from. |
@zfrisch imagine, |
@ljharb Wouldn’t that be |
@charmander to correctly extract it, you'd need const slice = ::Array.prototype.slice.call;
// or
const slice = ::[].slice.call;
slice(array); |
same question + 1 I need this feature. |
I'd like to champion this proposal and reshape it. But I first need ask the original champions or tc39 committee whether it was possible. |
I loved this feature when it was first introduced with babel. So sad seeing it die. |
FYI: There are currently three active rival TC39 proposals that are trying to subsume this inactive proposal:
There will be some further discussion at the next plenary meeting in January 2022 about these proposals (see “Holistic review of dataflow proposals” in tc39/agendas#1106). So there’s still ongoing activity in this problem space. |
Uh oh!
There was an error while loading. Please reload this page.
Are there any updates on the state of this proposal?
I find both the unary and the binary variant to be very useful and esthetic and I would definitely use them. The problem is that it hasn't been getting any updates for ages and the developers of libraries like TypeScript are afraid to implement it, because it's still an early draft.
So what is the current status of this feature? Is it going to get promoted to Stage 1 anytime soon?
The text was updated successfully, but these errors were encountered: