You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Node compat JS implementation, we generally follow Node.js source code as far as possible, but with _ prefix for private functions in a file (ex. afterConnect in lib/net.js in Node.js becomes _afterConnect in our code base). This _ prefix is confusing for comparing the 2 code bases. So we should remove them.
kt3k
changed the title
Do not prefix private function with _ in node compat JS implementation
refactor(ext/node): do not prefix private function with _ in node compat JS implementation
Nov 12, 2024
In Node compat JS implementation, we generally follow Node.js source code as far as possible, but with
_
prefix for private functions in a file (ex.afterConnect
inlib/net.js
in Node.js becomes_afterConnect
in our code base). This_
prefix is confusing for comparing the 2 code bases. So we should remove them.related: #26661 (comment)
The text was updated successfully, but these errors were encountered: