Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

go/types: assertion failure setting up composite literal with incomplete element type #27346

Closed
griesemer opened this issue Aug 29, 2018 · 3 comments
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@griesemer
Copy link
Contributor

This the std lib issue for golang/lint#411 . Small reproducer by @randall77:

package main

var x = [][n]int{
	0: {},
}

Issue: Checker.recordTypeAndValue called with nil argument. Need to determine where best to guard against this.

@griesemer griesemer self-assigned this Aug 29, 2018
@griesemer griesemer added the NeedsFix The path to resolution is known, but the work has not been done. label Aug 29, 2018
@griesemer griesemer added this to the Go1.11.1 milestone Aug 29, 2018
@FiloSottile FiloSottile modified the milestones: Go1.11.1, Go1.12 Aug 29, 2018
@FiloSottile
Copy link
Contributor

@gopherbot please file this for backport against 1.11. This is a regression.

@gopherbot
Copy link
Contributor

Backport issue(s) opened: #27351 (for 1.11).

Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://golang.org/wiki/MinorReleases.

@gopherbot
Copy link
Contributor

Change https://golang.org/cl/133415 mentions this issue: go/types: fix internal comments and add additional test case

@golang golang locked and limited conversation to collaborators Sep 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Development

No branches or pull requests

3 participants