GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — doc: add ReflectConstruct to known perf issues · nodejs/node@d4659e2

File tree

Expand file treeCollapse file tree
Open diff view settings
Filter options
  • doc/contributing
    • primordials.md
Expand file treeCollapse file tree
Open diff view settings
Collapse file

‎doc/contributing/primordials.md‎

Copy file name to clipboardExpand all lines: doc/contributing/primordials.md
+3Lines changed: 3 additions & 0 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -122,6 +122,9 @@ performance of code in Node.js.
122122
* `SafePromiseAny`
123123
* `SafePromiseRace`
124124
* `SafePromisePrototypeFinally`: use `try {} finally {}` block instead.
125+
* `ReflectConstruct`: Also affects `Reflect.construct`.
126+
`ReflectConstruct` creates new types of classes inside functions.
127+
Instead consider creating a shared class. See [nodejs/performance#109](https://github.com/nodejs/performance/issues/109).
125128

126129
In general, when sending or reviewing a PR that makes changes in a hot code
127130
path, use extra caution and run extensive benchmarks.

0 commit comments

Comments
0 (0)
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.