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
  • src
  • cmd
  • compile
  • internal
  • gc
  • bexport.go
Find file BlameHistoryPermalink
  • Robert Griesemer's avatar
    cmd/compile: have all or no parameter named in exported signatures · 80e9a7f0
    Robert Griesemer authored Apr 27, 2016
    Binary export format only.
    
    Make sure we don't accidentally export an unnamed parameter
    in signatures which expect all named parameters; otherwise
    we crash during import. Appears to happen for _ (blank)
    parameter names, as observed in method signatures such as
    the one at: x/tools/godoc/analysis/analysis.go:76.
    
    Fixes #15470.
    
    TBR=mdempsky
    
    Change-Id: I1b1184bf08c4c09d8a46946539c4b8c341acdb84
    Reviewed-on: https://go-review.googlesource.com/22543
    
    Reviewed-by: default avatarRobert Griesemer <gri@golang.org>
    80e9a7f0

Replace bexport.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