Closed Bug 1309784 Opened 8 years ago Closed 4 years ago

Add Cyclomatic Complexity

Categories

(Developer Documentation Graveyard :: JavaScript, defect, P5)

Product:
Developer Documentation Graveyard
Component:
JavaScript
Platform:
All
Other
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: tamir.daniely, Unassigned)

References

(
URL
)

Details

:: Developer Documentation Request

      Request Type: Correction
     Gecko Version: unspecified
 Technical Contact: 

:: Details

Add rough cyclomatic complexity counts for all calls so a reader can say compare Reflect.construct to new() based on let's call it "intended implementation" in those cases where the engine actually has to conform to at least reasonable performances. For example Set should always start as array and expand to a hashed set and Set.has() is theoretically guaranteed to be optimal. So the documentation should state such things. Also comparing new() and Reflect.construct(), it is clear that you can expect new() to always be faster then Reflect.construct(). This needs to be stated for novice learners.
Component: General → JavaScript
MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.
Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.