Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Contribute to GitLab
  • Sign in / Register
V
V8
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Linshizhi
  • V8
  • Repository

Switch branch/tag
  • v8
  • test
  • message
  • fail
  • var-conflict-in-with.out
Find file
BlameHistoryPermalink
  • Toon Verwaest's avatar
    [parser] Declare variables through ExpressionScope · c45850cd
    Toon Verwaest authored Jan 21, 2019
    Use variable tracking from ExpressionScopes rather than the PatternRewriter and
    PreParserExpression::variables_ to declare variables.
    
    We only figure out that variables are non-simple parameters once we see the
    first non-simple parameter. This still uses the pattern rewriter to make
    variables non-simple (kLet instead of kVar).
    
    Change-Id: I4a4ee4852d667c26806bb24896722cfea3e093f2
    Reviewed-on: https://chromium-review.googlesource.com/c/1417630Reviewed-by: 's avatarLeszek Swirski <leszeks@chromium.org>
    Commit-Queue: Toon Verwaest <verwaest@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#58954}
    c45850cd
var-conflict-in-with.out 177 Bytes
EditWeb IDE

Replace var-conflict-in-with.out

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.