1. 23 Mar, 2018 1 commit
    • Victor Costan's avatar
      Roll googletest to 1.8.0+. · 539e9072
      Victor Costan authored
      This is the V8 equivalent to https://crrev.com/2779193002 and must be landed
      before //build/secondary/{gtest,gmock} are removed from Chromium. This started
      out as https://crrev.com/2847693002
      
      The changes in tools/ were authored by yangguo@chromium.org and
      initially shared in http://crrev.com/2849783003.
      
      GoogleTest (gtest) and GoogleMock (gmock) are now hosted into the same
      googletest repository. In order to cope with this, the googletest
      repository is now sourced at third_party/googletest.
      
      The file/directory layout of Google Test is not yet considered stable.
      To minimize disruption while Google Test stabilizes, Chromium code will
      be insulated from third_party/googletest.
      
      * testing/gtest/include/gtest/ and testing/gmock/include/gmock have
        been populated with headers that forward into the appropriate
        locations of third_party/googletest
      
      * testing/BUILD.gn has been populated with the targets
        //testing/gtest(:gtest_main) and //testing/gmock(:gmock_main),
        which depend on the appropriate //third_party/googletest targets.
      
      All Chromium code should keep depending on the targets and
      headers in testing/{gtest,gmock} for now.
      
      BUG=chromium:630705
      
      Change-Id: I12b07ae78c8039aeff6ada7a3335e4e2b5d308ab
      Reviewed-on: https://chromium-review.googlesource.com/639953Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Commit-Queue: Victor Costan <pwnall@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#52170}
      539e9072
  2. 11 Apr, 2017 1 commit
    • gsathya's avatar
      [ESNext] Implement DynamicImportCall · 94283dcf
      gsathya authored
      This patch implements the runtime semantics of dynamic import.
      
      We create a new ASTNode so that we can pass the JSFunction closure() to
      the runtime function from which we get the script_url.
      
      d8 implements the embedder logic required to load and evaluate the modules.
      
      The API is mostly implemented as specified.
      
      BUG=8:5785
      
      Review-Url: https://codereview.chromium.org/2703563002
      Cr-Commit-Position: refs/heads/master@{#44551}
      94283dcf
  3. 17 Feb, 2017 1 commit
    • vabr's avatar
      Report unexpected lexical decl also without destructuring · 454816f0
      vabr authored
      https://codereview.chromium.org/2694003002/ introduced
      "SyntaxError: Lexical declaration cannot appear in a single-statement context"
      for the case when let + desctructuring from a list happen.
      
      As was pointed out in https://codereview.chromium.org/2694003002/#msg18, the
      case without destructuring would also benefit from a better message: if a
      single statement is expected and "let identifier = ..." is seen, the error is
      indeed again that the lexical declaration is not a statement. However, the current
      error is "Unexpected identifier", because the parser tries to accept "let" as
      an identifier in an expression statement, and then gives up seeing the other
      identifier after "let".
      
      This CL ensures that the parser recognises the error properly and reports
      accordingly. It also renames the existing test, which contains destructuring,
      and adds the one with a non-destructuring lexical declaration.
      
      BUG=v8:5686
      
      Review-Url: https://codereview.chromium.org/2697193007
      Cr-Commit-Position: refs/heads/master@{#43275}
      454816f0
  4. 16 Feb, 2017 1 commit
  5. 16 Jan, 2017 1 commit
  6. 12 Jan, 2017 1 commit
  7. 04 Jan, 2017 1 commit