« Bugzilla Issues Index
#1939 — 22.2.3.26: Invalid assertion in step 7
- bug_id:
1939
- creation_ts:
2013-09-27 07:59:00 -0700
- short_desc:
22.2.3.26: Invalid assertion in step 7
- delta_ts:
2013-09-27 14:47:49 -0700
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 18: September 5, 2013 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
normal
- everconfirmed:
true
- reporter:
André Bargull
- assigned_to:
Allen Wirfs-Brock
- commentid:
5466
- comment_count:
0
- who:
André Bargull
- bug_when:
2013-09-27 07:59:51 -0700
22.2.3.26 %TypedArray%.prototype.sort ( comparefn )
This assertion is not valid:
7. Assert: Both Type(x) and Type(y) is Number.
%TypedArray%.prototype.sort is a generic method, when applying it to an object which is not a %TypedArray%, this assertion does not hold.
Most likely other %TypedArray%.prototype functions also need to get a more formalised specification. The handwaving "may be optimized" opens the door for incompatible behaviour across implementations...
- commentid:
5485
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2013-09-27 11:50:28 -0700
No, I intentionally specified these methods as not being generic. That's why they are distinct functions and not just shared reference to the Array.prototype methods.
I added clarifying language and algorithms tweaks throughout 22.2.3
fixed in rev19 editor's draft
- commentid:
5488
- comment_count:
2
- who:
André Bargull
- bug_when:
2013-09-27 12:01:02 -0700
Ok, thanks for the clarification!
- commentid:
5578
- comment_count:
3
- who:
Allen Wirfs-Brock
- bug_when:
2013-09-27 14:47:49 -0700
fixed in rev19