Open
Bug 1435869
Opened 7 years ago
Updated 2 months ago
[META] Decorators proposal
Categories
(Core :: JavaScript Engine, enhancement, P3)
Core
JavaScript Engine
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox60 | --- | affected |
People
(Reporter: till, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug, )
Details
(Keywords: dev-doc-needed, meta)
While the Decorators proposal is only at stage 2, we should start getting implementation experience or at least an analysis of any potential performance concerns or other implementation hardships soon. There might be incidental implementation concerns that we could avoid by suggesting specific changes to the proposal but would otherwise have to live with if we wait too long.
Needinfo for Jason and André for the analysis part as discussed after the last tc39 meeting.
Flags: needinfo?(jorendorff)
Flags: needinfo?(andrebargull)
Updated•7 years ago
|
Keywords: dev-doc-needed
Reporter | ||
Comment 1•7 years ago
|
||
André, according to my notes you wanted to specifically look into how decorators interact with static class fields and their access to the class scope.
Comment 2•7 years ago
|
||
https://tc39.github.io/proposal-decorators/ builds upon https://tc39.github.io/proposal-private-methods/ and also includes https://tc39.github.io/proposal-class-fields/ and https://tc39.github.io/proposal-static-class-features/, so there's a bit of reading to do. Hopefully all four proposals were kept in sync, so they don't contradict each other (too much). :-)
But before diving into the decorators proposal, I should probably finish this other larger project (*cough* irregexp update *cough*).
Reporter | ||
Comment 3•7 years ago
|
||
(In reply to André Bargull [:anba] from comment #2)
> https://tc39.github.io/proposal-decorators/ builds upon
> https://tc39.github.io/proposal-private-methods/ and also includes
> https://tc39.github.io/proposal-class-fields/ and
> https://tc39.github.io/proposal-static-class-features/, so there's a bit of
> reading to do. Hopefully all four proposals were kept in sync, so they don't
> contradict each other (too much). :-)
Dan, can you comment on whether this assumption holds? I'm assuming largely yes, but would be good to be sure.
Flags: needinfo?(littledan)
Comment 4•7 years ago
|
||
I've done my best to keep the proposals in sync, but bug reports are always welcome. Among these, I'd recommend starting with private methods and class fields, which are Stage 3 and more stable. Static class features and decorators are likely to have some tweaks to them on their way to Stage 3.
If any SpiderMonkey engineers are interested, I'd like to go over decorator semantics in detail with JS implementers in a call, in preparation for proposing to Stage 3 at TC39. Who should I send an invitation to?
Flags: needinfo?(littledan)
Updated•7 years ago
|
Flags: needinfo?(jorendorff)
Priority: -- → P3
Updated•6 years ago
|
Flags: needinfo?(andrebargull)
Updated•3 years ago
|
Comment 6•3 years ago
•
|
||
This is conditionally advanced. The primary issue of metadata has been fixed, we are waiting on isPrivate
(https://github.com/tc39/proposal-decorators/issues/417) and a few other changes.
Updated•2 years ago
|
Assignee: nobody → dminor
Updated•2 years ago
|
Summary: Implement Decorators proposal → [META] Decorators proposal
Updated•2 years ago
|
Severity: normal → S3
Updated•2 years ago
|
Severity: S3 → N/A
Just curious, has the team started implementation of stage 3 decorators yet? It is going to be incredibly awesome.
Comment 8•1 year ago
|
||
Yes, the implementation is being tracked by Bug 1781212.
Updated•3 months ago
|
Assignee: dminor → nobody
You need to log in
before you can comment on or make changes to this bug.
Description
•