Skip to content

docs: be specific about the unit of maxBuffer #209

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
wants to merge 1 commit into from

Conversation

timruffles
Copy link
Contributor

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

@bnoordhuis
Copy link
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 timruffles force-pushed the doc-max-buffer branch 2 times, most recently from be31479 to 5eb984f Compare December 29, 2014 19:03
the maxBuffer option was not self-documenting, so document
unit and its effect.
@timruffles
Copy link
Contributor Author

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
Member

Cheers Tim, landed in 6f49c24.

@bnoordhuis bnoordhuis closed this Dec 30, 2014
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.
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants