« Bugzilla Issues Index
#2965 — 7.3.16 GetPrototypeFromConstructor, 22.1.3.* Array.prototype.*: Use BoundFunctionTargetRealm to retrieve [[Realm]] of bound functions?
- bug_id:
2965
- creation_ts:
2014-06-02 09:59:00 -0700
- short_desc:
7.3.16 GetPrototypeFromConstructor, 22.1.3.* Array.prototype.*: Use BoundFunctionTargetRealm to retrieve [[Realm]] of bound functions?
- delta_ts:
2014-07-18 20:48:58 -0700
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 25: May 22, 2014 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
enhancement
- everconfirmed:
true
- reporter:
André Bargull
- assigned_to:
Allen Wirfs-Brock
- commentid:
8802
- comment_count:
0
- who:
André Bargull
- bug_when:
2014-06-02 09:59:37 -0700
7.3.16 GetPrototypeFromConstructor ( constructor, intrinsicDefaultProto )
22.1.3.1 Array.prototype.concat ( ...arguments )
22.1.3.7 Array.prototype.filter ( callbackfn [ , thisArg ] )
22.1.3.15 Array.prototype.map ( callbackfn [ , thisArg ] )
22.1.3.22 Array.prototype.slice (start, end)
22.1.3.25 Array.prototype.splice (start, deleteCount [ , ...items ] )
These functions / abstract operations currently use [[Realm]] to retrieve the Realm record. That means only ECMAScript and built-in function objects are handled. Does it make sense to extend the checks to include bound functions, now that BoundFunctionTargetRealm is available?
- commentid:
9150
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2014-07-10 15:47:39 -0700
Fixed in rev26 editor's draft.
Replaced BoundFunctionTargetRealm with a more general getFrunctionRealm that works will all callables.
- commentid:
9299
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2014-07-18 20:48:58 -0700
Fixed in Rev26