-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
gccgo: does not permit conversion of slice ignoring struct tags #50439
Labels
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Comments
Looks like a bug in gccgo. Thanks. |
Change https://golang.org/cl/375796 mentions this issue: |
Change https://golang.org/cl/375797 mentions this issue: |
gopherbot
pushed a commit
that referenced
this issue
Jan 6, 2022
For #50439 Change-Id: Ifad6e6f8de42121c695b5a4dc56e0f6606e2917e Reviewed-on: https://go-review.googlesource.com/c/go/+/375796 Trust: Ian Lance Taylor <iant@golang.org> Run-TryBot: Ian Lance Taylor <iant@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Than McIntosh <thanm@google.com> Trust: Than McIntosh <thanm@google.com> Reviewed-by: Cherry Mui <cherryyz@google.com>
nstester
pushed a commit
to nstester/gcc
that referenced
this issue
Jan 6, 2022
jproberts
pushed a commit
to jproberts/go
that referenced
this issue
Jun 21, 2022
For golang#50439 Change-Id: Ifad6e6f8de42121c695b5a4dc56e0f6606e2917e Reviewed-on: https://go-review.googlesource.com/c/go/+/375796 Trust: Ian Lance Taylor <iant@golang.org> Run-TryBot: Ian Lance Taylor <iant@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Than McIntosh <thanm@google.com> Trust: Than McIntosh <thanm@google.com> Reviewed-by: Cherry Mui <cherryyz@google.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What did you do?
What did you expect to see?
Same behavior
What did you see instead?
The text was updated successfully, but these errors were encountered: