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
From looking at the source, I see decorators simply return () => {}, which I think implies that they are used only during a compile step (no runtime implementation).
Do you have any thoughts on the new decorator format, in particular the problems and solution I described here?:
I'm trying to get all the feedback I can there. It seems not enough people who actually use decorators are involved in the iscussions there.
Maybe decorators for your case are only significant as compiler annotations, which would still be interesting to hear about. If you do have runtime use cases, that would be great to learn about too.
The text was updated successfully, but these errors were encountered:
From looking at the source, I see decorators simply return
() => {}
, which I think implies that they are used only during a compile step (no runtime implementation).Do you have any thoughts on the new decorator format, in particular the problems and solution I described here?:
discrepancy: we're allowed to get/set private fields, but not public fields, and public auto accessors are not fields.
I'm trying to get all the feedback I can there. It seems not enough people who actually use decorators are involved in the iscussions there.
Maybe decorators for your case are only significant as compiler annotations, which would still be interesting to hear about. If you do have runtime use cases, that would be great to learn about too.
The text was updated successfully, but these errors were encountered: