Make catch clause variables optional

Michael Ficarra (@michaelficarra)

The proposal by Michael Ficarra (@michaelficarra) makes the binding identifier in catch clauses optional.

For example:

try {
    JSON.parse("...");
}
catch {
    // Don't care, the error message is completely useless,
    // but we need to handle it.
}

This proposal reached stage 3 immediately upon presentation.

🚲 🏠 what should we name the variable when downleveling?

I was thinking unexpectedTokenInJsonAtPositionError.

I'd vote 🤷‍♀️, with further downleveling as appropriate.

The page is moved to https://tc39.github.io/proposal-optional-catch-binding/, for someone who wants to track the change of TS 2.5.

Just a thought but how about having the catch block itself as optional?

For example we have the 'traditional' try catch:

try {
    // Something risky
} catch (e) {
    // Handle the specifics of e
}
// Continue

The 'I don't care what went wrong' try catch:

try {
    // Something risky
} catch {
    // ¯\_(ツ)_/¯, Something happen lets do this instead
}
// Continue

So how about a 'I don't care' try (catch):

try {
    // Something risky
}
// Continue

That would be a good suggestion for ESDiscuss and I am sure that TypeScript would follow suit if the proposal made it. Diverging outside of that just in TypeScript wouldn't likely make sense.

Navigation Menu

Repository navigation

Make catch clause variables optional #17467

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Make catch clause variables optional #17467

Description

Activity

RyanCavanaugh commented on Jul 27, 2017

DanielRosenwasser commented on Jul 27, 2017

jwbay commented on Jul 28, 2017

saschanaz commented on Aug 14, 2017

ZanderBrown commented on Aug 31, 2017

kitsonk commented on Aug 31, 2017

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions