Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • G go
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Smelkov
  • go
  • Repository

Switch branch/tag
  • go
  • test
  • fixedbugs
  • issue32133.go
Find file BlameHistoryPermalink
  • Robert Griesemer's avatar
    cmd/compile: avoid follow-on errors for literals with syntax errors · 5411953d
    Robert Griesemer authored Aug 29, 2019
    - only convert literal strings if there were no syntax errors
      (some of the conversion routines exit if there is an error)
    - mark nodes for literals with syntax errors to avoid follow-on
      errors
    - don't attempt to import packages whose path had syntax errors
    
    Fixes #32133.
    
    Change-Id: I1803ad48c65abfecf6f48ddff1e27eded5e282c5
    Reviewed-on: https://go-review.googlesource.com/c/go/+/192437
    
    Reviewed-by: default avatarMatthew Dempsky <mdempsky@google.com>
    5411953d

Replace issue32133.go

Attach a file by drag & drop or click to upload


Cancel
GitLab will create a branch in your fork and start a merge request.
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7