Skip to content

docs: be specific about the unit of maxBuffer - #209

Closed
timruffles wants to merge 1 commit into
nodejs:v0.12from
timruffles:doc-max-buffer
Closed

docs: be specific about the unit of maxBuffer#209
timruffles wants to merge 1 commit into
nodejs:v0.12from
timruffles:doc-max-buffer

Conversation

@timruffles

Copy link
Copy Markdown
Contributor

It's nice to be specific about units in docs.

@bnoordhuis

Copy link
Copy Markdown
Member

Please wrap lines at 80 columns. Apart from that, LGTM. If you update the PR, and maybe amend the commit log so it's not a one-liner, I'll land it.

@timruffles
timrufflesforce-pushed the doc-max-buffer branch 2 times, most recently from be31479 to 5eb984fCompareDecember 29, 2014 19:03
the maxBuffer option was not self-documenting, so document
unit and its effect.
@timruffles

Copy link
Copy Markdown
ContributorAuthor

Done

bnoordhuis pushed a commit to bnoordhuis/io.js that referenced this pull request Dec 30, 2014
The maxBuffer option was not self-documenting, so document the unit and
its effect.
PR-URL: nodejs#209
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
@bnoordhuis

Copy link
Copy Markdown
Member

Cheers Tim, landed in 6f49c24.

syg pushed a commit to syg/node that referenced this pull request May 5, 2025
Isolate::AttachCppHeap is about to be deprecated soon, the CppHeap
should be provided during Isolate initialization instead.
bakkot pushed a commit to bakkot/node that referenced this pull request May 11, 2026
Isolate::AttachCppHeap is about to be deprecated soon, the CppHeap
should be provided during Isolate initialization instead.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@timruffles@bnoordhuis