Closed
Bug 1019334
Opened 11 years ago
Closed 11 years ago
Remove TypedArray's (JSObject*) constructor overload
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla32
People
(Reporter: Waldo, Assigned: Waldo)
Details
Attachments
(1 file)
|
5.03 KB,
patch
|
bzbarsky
:
review+
|
Details | Diff | Splinter Review |
TypedArray's object-taking constructor is sort of broken. Remove it.
| Assignee | ||
Comment 1•11 years ago
|
||
Attachment #8432945 -
Flags: review?(bzbarsky)
Comment 2•11 years ago
|
||
Comment on attachment 8432945 [details] [diff] [review]
Patch
Why not just have the one-arg ctor call Init() instead of making all the consumers do it?
Flags: needinfo?(jwalden+bmo)
| Assignee | ||
Comment 3•11 years ago
|
||
Because then people have to check inited() themselves, manually, and remember to do it. Whereas if Init() is required to do anything, there's an existing call that must be made, and the burden of checking its return value is somewhat more obvious.
Flags: needinfo?(jwalden+bmo)
Comment 4•11 years ago
|
||
Comment on attachment 8432945 [details] [diff] [review]
Patch
OK, that's fair. I had mostly designed this constructor for those cases where you're MOZ_ASSERTing inited, but alright.
Attachment #8432945 -
Flags: review?(bzbarsky) → review+
| Assignee | ||
Comment 5•11 years ago
|
||
Comment 6•11 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla32
Updated•7 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•