-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
Support 'throw' expressions #18535
Comments
Just to note, @rbuckton is closely aligned to the TypeScript team. I highly suspect this proposal would be implemented when everyone is comfortable it is in a stable enough position. |
@kitsonk That make sense. |
Nope, it's fine to track it here. Like @kitsonk said, @rbuckton is championing it and is part of our team, but we will need it to reach a later stage before adopting it in TypeScript. For what it's worth, I'd be willing to bet he has a branch with an implementation of |
https://github.com/Microsoft/TypeScript/tree/throwOperator?files=1 Currently it does not yet support unreachability checks at the expression level. Also, I am waiting for the next TC39 meeting to see if the proposal moves to Stage 2. |
@DanielRosenwasser @rbuckton |
The proposal is now in stage 2 - would be cool if this gets implemented in TypeScript. |
TypeScript's current stance is that we will not adopt a proposed JavaScript feature until it has reached Stage 3. Currently, Stage 3 for |
Ah, I see. Thanks, @rbuckton! |
This is now in stage 3 :) |
No, this has not yet advanced to Stage 3. |
Closing since there's nothing for us to do but wait for TC39 |
Support proposal-throw-expressions.
That proposal is now stage-1, but worth to implements for convenience and this proposal not break backward-compatibilities.
Current
ts
js
Proposal
ts
js
The text was updated successfully, but these errors were encountered: