| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
hmm... not sure there's enough value at this point with v6 right around the corner. If we were going to pull this back to v4 then I think I'd be +1 for sure. |
Sorry, something went wrong.
|
@jasnell I figured we would probably not want it... but had already made the patch and it was small enough I figured we might want to be explicit |
Sorry, something went wrong.
|
this would need to be rebased now ;-) |
Sorry, something went wrong.
|
LGTM but can you capitalize 'while' and use 'Refs:' in the commit log? |
Sorry, something went wrong.
|
LGTM, but may be we should just turn the only let here to var instead? |
Sorry, something went wrong.
|
I've updated with both of your suggestions @bnoordhuis / @indutny PTAL and let me know if this is ok |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
While `let` no longer needs to run in `strict mode` in v8 5.x it throws in v8 4. This modification will make the test-vm-cached-data work in older version of node. Refs: nodejs#6280 PR-URL: nodejs#6317 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: Michaël Zasso <mic.besace@gmail.com>
While `let` no longer needs to run in `strict mode` in v8 5.x it throws in v8 4. This modification will make the test-vm-cached-data work in older version of node. Refs: #6280 PR-URL: #6317 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: Michaël Zasso <mic.besace@gmail.com>
| Back | FazBrowse Home | New Git URL |
while let no longer needs to run in strict mode in v8 5.x it throws
in v8 4. This modification will make the test-vm-cached-data work in
older version of node.
I am under the impression that these changes were made to test features that will only be available in v8 5. So perhaps we don't care to support older versions. Either way it might be nice to be explicit with the code being shelled out.
I've currently marked #6280 as dont-land-on-v5.x, but we can change that if this lands
/cc @jasnell @indutny