| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
concept seems good, can't comment on the python though |
Sorry, something went wrong.
There was a problem hiding this comment.
Can you use two-space indent in this file?
Sorry, something went wrong.
There was a problem hiding this comment.
@bnoordhuis Done!
Sorry, something went wrong.
|
Looks like you missed one though, unless the CI is outdated. File "src/handle_wrap.cc" does not use "Boolean" Makefile:632: recipe for target 'cpplint' failed |
Sorry, something went wrong.
|
@Fishrock123 Hmmm, weird! I ran the linter locally before pushing. Anyway, I fixed it and the new CI Run (https://ci.nodejs.org/job/node-test-pull-request/2211/) completed linting successfully. |
Sorry, something went wrong.
There was a problem hiding this comment.
Can you remove the trailing blank line? Aside, you don't strictly need the square brackets in the line above but it doesn't hurt either.
Sorry, something went wrong.
There was a problem hiding this comment.
@bnoordhuis Actually, that is necessary. all and any short-circuit. They return True and False the moment they meet an item doesn't meet the criteria. Passing a generator expression will leave the rest of them unexecuted. For example,
>>> gen = (num for num in xrange(10))
>>> all(item * item < 20 for item in gen)
False
>>> list(gen)
[6, 7, 8, 9]But when we use List Comprehension, it executes all of them and only their results are used with all and any. For example,
>>> gen = (num for num in xrange(10))
>>> all([item * item < 20 for item in gen])
False
>>> list(gen)
[]Wrote more about it in this StackOverflow answer
Sorry, something went wrong.
|
LGTM with a style nit. I'm somewhat ambivalent about the rewrite to python, the new script is two or three times as long as the old one (if you exclude the copyright boilerplate.) |
Sorry, something went wrong.
|
@bnoordhuis The other reason I rewrote it in Python was because, if this is included in the linter, all the development environments are supposed to have sed, grep, sort and etc. That may not be available in all the environments I guess. I am okay with retaining the shell script itself, if possible. |
Sorry, something went wrong.
There was a problem hiding this comment.
What would you think of using filename instead of file? I’d find that more a bit readable + it doesn’t shadow the file built-in.
Sorry, something went wrong.
There was a problem hiding this comment.
@addaleax I don't know how I missed that. Thanks for catching it :-) Fixed it now.
Sorry, something went wrong.
As it is, check-install.sh does not show more helpful error messages, and supporting various shells could be a problem. This patch rewrites the same in Python.
This patch simply enables check-imports.py in the linting process
|
As this patch adds a new linter task to the build process, ccing @nodejs/build |
Sorry, something went wrong.
|
If there are no objections, I'll land this in two days. cc @nodejs/collaborators |
Sorry, something went wrong.
|
LGTM, finally! |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
As it is, check-install.sh does not show more helpful error messages, and supporting various shells could be a problem. This patch rewrites the same in Python. This patch also enables check-imports.py in the linting process PR-URL: #6105 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
This patch fixes all the linter errors. PR-URL: #6105 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
As it is, check-install.sh does not show more helpful error messages, and supporting various shells could be a problem. This patch rewrites the same in Python. This patch also enables check-imports.py in the linting process PR-URL: nodejs#6105 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
This patch fixes all the linter errors. PR-URL: nodejs#6105 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
As it is, check-install.sh does not show more helpful error messages, and supporting various shells could be a problem. This patch rewrites the same in Python. This patch also enables check-imports.py in the linting process PR-URL: #6105 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
This patch fixes all the linter errors. PR-URL: #6105 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
This patch fixes all the linter errors. PR-URL: #6105 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
|
@thefourtheye should this be backported? |
Sorry, something went wrong.
|
@thealphanerd There is no harm in backporting this, but I am not sure if it is absolutely necessary :( |
Sorry, something went wrong.
|
@thefourtheye this does not land cleanly. I'm adding the dont-land label. Feel free to send a backport PR if you would like, but I don't see it as pressing |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Checklist
Affected core subsystem(s)
src, tools
Description of change
Commit 1
As it is, check-install.sh does not show more helpful error messages,
and supporting various shells could be a problem. This patch rewrites
the same in Python.
Commit 2
This patch simply enables check-imports.py in the linting process
Commit 3
Fix all the linter errors
cc @bnoordhuis
CI Run: https://ci.nodejs.org/job/node-test-pull-request/2210/