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

chore: prefer "any" to "interface{}" #305

Merged
merged 1 commit into from
Apr 22, 2024
Merged

chore: prefer "any" to "interface{}" #305

merged 1 commit into from
Apr 22, 2024

Conversation

blgm
Copy link
Member

@blgm blgm commented Apr 22, 2024

In Go, "any" was introduced alongside generics because the empty interface "interface{}" was considered a bit confusing. They mean the same thing, and code with "any" is a bit easier to understand and looks more modern. Test fakes were not updated as they are generated code.

In Go, "any" was introduced alongside generics because the empty
interface "interface{}" was considered a bit confusing. They mean the
same thing, and code with "any" is a bit easier to understand and looks
more modern. Test fakes were not updated as they are generated code.
@cf-gitbot
Copy link
Member

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/187474858

The labels on this github issue will be updated when the story is started.

@blgm blgm merged commit 9ca5e22 into main Apr 22, 2024
4 checks passed
@blgm blgm deleted the interface branch April 22, 2024 14:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants