« Bugzilla Issues Index
#2586 — 15.2.4.3 No need to return a promise
- bug_id:
2586
- creation_ts:
2014-03-23 13:48:00 -0700
- short_desc:
15.2.4.3 No need to return a promise
- delta_ts:
2015-03-16 14:42:11 -0700
- product:
Draft for 6th Edition
- component:
deferred features
- version:
Rev 22: January 20, 2014 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
WONTFIX
- priority:
Normal
- bug_severity:
normal
- everconfirmed:
true
- reporter:
Guy Bedford
- assigned_to:
Allen Wirfs-Brock
- cc:
["dherman", "jorendorff", "samth"]
- commentid:
7458
- comment_count:
0
- who:
Guy Bedford
- bug_when:
2014-03-23 13:48:11 -0700
The return promise value of ProceedToLocate is never used by its callers.
- commentid:
10151
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2014-09-03 17:49:29 -0700
it could be an abrupt completion.
We need to work out the exception paths and make sure that they get handled or reported appropriately and not just dropped.
- commentid:
10166
- comment_count:
2
- who:
Guy Bedford
- bug_when:
2014-09-08 08:40:13 -0700
Surely the presence or not of the `return` statement doesn't affect the execution though?
ProceedToLocate itself takes the value from ProceedToFetch, takes the value from ProceedToTranslate, which is undefined.
The only logic in these functions is promise construction.
So in terms of the exception paths, there is no exception handling at this level to worry about, unless the global Promise becomes undefined, or gets manipulated so that `.then` stops working?
- commentid:
13774
- comment_count:
3
- who:
Allen Wirfs-Brock
- bug_when:
2015-03-16 14:42:11 -0700
concerns old module spec.