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

gc: wrong output from %lN #2449

Closed
rsc opened this issue Nov 11, 2011 · 6 comments

Comments

Projects
None yet
3 participants
@rsc
Copy link
Contributor

commented Nov 11, 2011

I added an error check for switch on a func/map/slice to
ensure that the only valid case is nil.  The error print says

    yyerror("invalid case %N in switch (can only compare %lN to nil)", ll->n, n->ntest);

and then the error says

    bytes_test.go:698: invalid case bytes.Trim in switch (can only compare tc.f (type func(? []byte, ? string) []byte) to nil)

The question marks should not be there.
@rsc

This comment has been minimized.

Copy link
Contributor Author

commented Nov 11, 2011

Comment 1:

Owner changed to @lvdlvd.

@lvdlvd

This comment has been minimized.

Copy link

commented Nov 14, 2011

Comment 2:

oops, that happened in the fix for .anon.   cl coming up.
@lvdlvd

This comment has been minimized.

Copy link

commented Nov 14, 2011

Comment 3:

Labels changed: added compilerbug.

@rsc

This comment has been minimized.

Copy link
Contributor Author

commented Dec 9, 2011

Comment 4:

Labels changed: added priority-later, removed priority-medium.

@rsc

This comment has been minimized.

Copy link
Contributor Author

commented Dec 12, 2011

Comment 5:

Labels changed: added priority-go1.

@lvdlvd

This comment has been minimized.

Copy link

commented Dec 13, 2011

Comment 6:

fixed in ab293785bbcc

Status changed to Fixed.

@rsc rsc added fixed labels Dec 13, 2011

@rsc rsc added this to the Go1 milestone Apr 10, 2015

@rsc rsc removed the priority-go1 label Apr 10, 2015

@golang golang locked and limited conversation to collaborators Jun 24, 2016

This issue was closed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.