Skip to content

Conversation

sam-github
Copy link
Contributor

@sam-github sam-github commented May 16, 2017

Backport of #12241 to 7.x

Also rolled in #12648, because it depends on the use of std::vector.

A dynamically allocated array was being used, simplify the memory
management by using std::vector.

PR-URL: #12241
Reviewed-By: Richard Lau [email protected]
Reviewed-By: James M Snell [email protected]
Reviewed-By: Daniel Bevenius [email protected]
Reviewed-By: Colin Ihrig [email protected]
Reviewed-By: Anna Henningsen [email protected]

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)

@nodejs-github-bot nodejs-github-bot added c++ Issues and PRs that require attention from people who are familiar with C++. v7.x labels May 16, 2017
@sam-github sam-github changed the title src: use a std::vector for preload_modules (7.x backport) src: use a std::vector for preload_modules May 16, 2017
@watilde
Copy link
Contributor

watilde commented May 16, 2017

A dynamically allocated array was being used, simplify the memory
management by using std::vector.

PR-URL: nodejs#12241
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Daniel Bevenius <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
@sam-github sam-github force-pushed the backport-12241-use-vector-for-preload-modules branch from 9a8f38e to 3ab322f Compare May 18, 2017 16:19
@sam-github sam-github changed the title (7.x backport) src: use a std::vector for preload_modules (7.x backport) NODE_OPTIONS, and one of its dependant refactors May 18, 2017
Not all CLI options are supported, those that are problematic from a
security or implementation point of view are disallowed, as are ones
that are inappropriate (for example, -e, -p, --i), or that only make
sense when changed with code changes (such as options that change the
javascript syntax or add new APIs).

PR-URL: nodejs#12028
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
Reviewed-By: Refael Ackermann <[email protected]>
Reviewed-By: Gibson Fahnestock <[email protected]>
Reviewed-By: Bradley Farias <[email protected]>
@sam-github sam-github force-pushed the backport-12241-use-vector-for-preload-modules branch from 3ab322f to 3f6199c Compare May 18, 2017 16:30
@sam-github
Copy link
Contributor Author

@sam-github
Copy link
Contributor Author

@nodejs/release How do things land on v7.x-staging? Can I land this? Does someone from release?

@sam-github
Copy link
Contributor Author

Hm, @gibfahn points out that people seem to land themselves: https://github.com/nodejs/node/pulls?utf8=%E2%9C%93&q=is%3Apr%20is%3Aclosed%20base%3Av7.x-staging%20

So, I will.

@sam-github sam-github merged commit 3f6199c into nodejs:v7.x-staging May 19, 2017
@sam-github sam-github deleted the backport-12241-use-vector-for-preload-modules branch May 26, 2017 17:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

c++ Issues and PRs that require attention from people who are familiar with C++.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants