Closed
Bug 1452692
Opened 7 years ago
Closed 7 years ago
Array.apply(a,b) is not a constructor, Array(b) would be a constructor
Categories
(Developer Documentation Graveyard :: JavaScript, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: horusscope, Assigned: cmills)
References
()
Details
:: Developer Documentation Request
Request Type: Correction
Gecko Version: unspecified
Technical Contact:
:: Details
Quote from page (/Functions/arguments)
"An alternative would be to use the despised Array constructor as a function:
[...] : Array.apply(null, arguments));"
Array(arguments) is a gorgeous constructor, the use of disparaging language feels inappropriate at best
However, apply is not a constructor, it is a function dispatch prototype as I'm sure you're aware; which makes the content semantically inaccurate
MDN generally presents itself as a resource and not a wiki page, and carries that amount of respect
Updated•7 years ago
|
Priority: -- → P2
Assignee | ||
Comment 1•7 years ago
|
||
I agree - I think as well as being a silly use of language for a reference article, it is also incorrect.
I've updated the wording to something more appropriate. Thanks for reporting.
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → cmills
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•