Skip to content
This repository has been archived by the owner before Nov 9, 2022. It is now read-only.

tc39/proposal-optional-catch-binding

master
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Code

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
 
 
 
 
 
 

This proposal makes a grammatical change to ECMAScript, allowing the omission of a catch binding in cases where the binding would not be used. This occurs frequently with patterns such as

try {
  // try to use a web feature which may not be implemented
} catch (unused) {
  // fall back to a less desirable web feature with broader support
}

or

let isTheFeatureImplemented = false;
try {
  // stress the required bits of the web API
  isTheFeatureImplemented = true;
} catch (unused) {}

or

let parseResult = someFallbackValue;
try {
  parseResult = JSON.parse(potentiallyMalformedJSON);
} catch (unused) {}

and it is a common opinion that variables which are declared or written to but never read signify a programming error.

The grammar change introduced by this proposal allows for the catch binding and its surrounding parentheses to be omitted, as in

try {
  // ...
} catch {
  // ...
}

See the the full text of the proposal for more info.

About

proposal for ECMAScript to allow omission of the catch binding

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published