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.

Sign up for GitHub

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

Jump to bottom

all: rewrite interface{} to any #49884

Closed
griesemer opened this issue Nov 30, 2021 · 14 comments
Closed

all: rewrite interface{} to any #49884

griesemer opened this issue Nov 30, 2021 · 14 comments
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done. release-blocker
Milestone
Go1.18

Comments

@griesemer
Copy link
Contributor

Reminder issue.
@griesemer griesemer added NeedsFix The path to resolution is known, but the work has not been done. release-blocker labels Nov 30, 2021
@griesemer griesemer added this to the Go1.18 milestone Nov 30, 2021
@griesemer
Copy link
Contributor Author

The type checker preserves the difference between interface{} and any (it keeps track of the alias in this case, like it does for byte and uint8), so tests that rely on printing interface{} as "interface{}" must remain unchanged. And so should tests in testdata directories.

@griesemer griesemer changed the title all: rewrite "interface{}" to "any" all: rewrite interface{} to any Nov 30, 2021
@griesemer
Copy link
Contributor Author

@findleyr Please comment here once you're satisfied with the handling of any in the importers.

@gopherbot
Copy link
Contributor

Change https://golang.org/cl/368254 mentions this issue: all: gofmt -w -r 'interface{} -> any' src

@AlphaHot
Copy link

AlphaHot commented Dec 2, 2021 •
edited
Loading

No, please don't do that. I'm used to the interface{}.

@ii64

This comment has been minimized.

Sign in to view
@kostyaBro
Copy link

What problem does this solve? Can you describe?

It also seems to me to break backward compatibility.

@cristaloleg
Copy link

No, it doesn't break backward compatibility, see original issue/proposal. any is just an alias for interface{}.

@rsc
Copy link
Contributor

rsc commented Dec 7, 2021

This is not the issue, nor the time, to debate allowing any. This issue is about tracking certain work. Regarding allowing any at all, we had the proposal discussion, and the proposal was accepted. See #33232 (comment) for the rationale. No one is raising any new information that would warrant reopening the decision.

@gopherbot
Copy link
Contributor

Change https://golang.org/cl/369955 mentions this issue: go/internal/gcimporter: fix test for Go 1.18 any

gopherbot pushed a commit to golang/tools that referenced this issue Dec 7, 2021
@rsc
go/internal/gcimporter: fix test for Go 1.18 any
d3358c1 
In Go 1.18 context uses any, not interface{}.
Fix the test in a way that should work for both older and newer versions.

For golang/go#49884.

Change-Id: Ib8690876c6a9364b98f9c7ba739b953a8d7565d4
Reviewed-on: https://go-review.googlesource.com/c/tools/+/369955
Trust: Russ Cox <rsc@golang.org>
Run-TryBot: Russ Cox <rsc@golang.org>
gopls-CI: kokoro <noreply+kokoro@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
Reviewed-by: Robert Findley <rfindley@google.com>
@gopherbot
Copy link
Contributor

Change https://golang.org/cl/370294 mentions this issue: internal/lsp: normalize interface{} to any in test comparisons

gopherbot pushed a commit to golang/tools that referenced this issue Dec 9, 2021
@findleyr @rsc
internal/lsp: normalize interface{} to any in test comparisons
e06c107 
The switch to use any in standard library signatures breaks many of our
tests that match signature strings exactly. Fix this by normalizing
strings to use 'any' in place of interface{}, before comparing.

Updates golang/go#49884

Change-Id: If18ce1035b3206f37d7de6e584cf2c2cae9481c5
Reviewed-on: https://go-review.googlesource.com/c/tools/+/370294
Trust: Robert Findley <rfindley@google.com>
Run-TryBot: Robert Findley <rfindley@google.com>
gopls-CI: kokoro <noreply+kokoro@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
Reviewed-by: Russ Cox <rsc@golang.org>
@toothrot
Copy link
Contributor

Friendly check-in here, this is one of the last two issues blocking the beta of 1.18. Has there been an update recently?

@gopherbot
Copy link
Contributor

Change https://golang.org/cl/371297 mentions this issue: net/http: revert h2_bundle.go formatting change from CL 368254

gopherbot pushed a commit that referenced this issue Dec 13, 2021
net/http: revert h2_bundle.go formatting change from CL 368254
9e85dc5 
h2_bundle.go is automatically generated from x/net/http2. Any
formatting changes within that file need to be first made upstream.

This brings the contents of h2_bundle.go back in line with the
upstream generator, fixing the cmd/internal/moddeps test that is
currently failing on the longtest builders.

For #49884

Change-Id: I5757240b77e250e0026b8a52a0e867e1578ec2d4
Reviewed-on: https://go-review.googlesource.com/c/go/+/371297
Trust: Bryan Mills <bcmills@google.com>
Run-TryBot: Bryan Mills <bcmills@google.com>
Reviewed-by: David Chase <drchase@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
@seankhliao
Copy link
Member

Do doc comments need to be updated or are they fine to be left as interface{} ?

@griesemer
Copy link
Contributor Author

@seankhliao This is issue is closed. Please continue this discussion elsewhere.

That said: it depends. Simply replacing interface{} with any may lead to grammatically incorrect or funny sounding prose. It probably takes some tuning to get right.

But again, please discuss this elsewhere.

@ZekeLu ZekeLu mentioned this issue Jan 13, 2022
Closed
@thanm thanm mentioned this issue Jan 25, 2022
Open
@vmg vmg mentioned this issue Mar 18, 2022
Merged
3 tasks
@rsc rsc removed their assignment Jun 23, 2022
@gaius-qi gaius-qi mentioned this issue Jun 30, 2022
Merged
8 tasks
@liuyang1520 liuyang1520 mentioned this issue Jul 15, 2022
Merged
1 task
@Olshansk Olshansk mentioned this issue Aug 8, 2022
Closed
1 task
@johanbrandhorst johanbrandhorst mentioned this issue Oct 11, 2022
Merged
@Marton6 Marton6 mentioned this issue Dec 5, 2022
Merged
@golang golang locked and limited conversation to collaborators Jun 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done. release-blocker
Projects
None yet
Milestone
Go1.18
Development

No branches or pull requests
9 participants
@toothrot @rsc @cristaloleg @griesemer @gopherbot @seankhliao @kostyaBro @ii64 @AlphaHot