Rename Promise.catch() to something else

RESOLVED WONTFIX

Status

()

Core
DOM
RESOLVED WONTFIX
5 years ago
4 years ago

People

(Reporter: mounir, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
Future.catch() has the problem of using an EcmaScript reserved name and old browsers will not enjoy that. This is the same probleme with .delete() in IDB. Developers have to do idb['delete']() to be able to have the code parsed (not even executed) in all browsers. Might be a pain if developers have to do that with catch.

Comment 1

5 years ago
'fail', like in the Q library?
Anne, can you give a feedback about this?
Flags: needinfo?(annevk)

Comment 3

5 years ago
This ground has been covered in the spec discussion. ES5 happened, we're gonna use the terms that make the most sense.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Flags: needinfo?(annevk)
Resolution: --- → WONTFIX
(Reporter)

Comment 4

5 years ago
Please, keep this bug open until the discussion happened in a public place.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Summary: Rename Future.catch() to something else → Rename Promise.catch() to something else
I don't think this is what we want. Do we really want to rename catch() ?
Flags: needinfo?(annevk)

Comment 6

4 years ago
No. (And to address comment 4, this discussion did happen in a public place.)
Status: REOPENED → RESOLVED
Last Resolved: 5 years ago4 years ago
Flags: needinfo?(annevk)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.