You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This framework generally requires heavy usage of empty interface types (interface{}, []interface{}, map[string]interface{}) when working with helper/schema.ResourceData. This syntax is a little verbose and is not intuitive for newer provider developers or Gophers coming from projects which typically use concrete types.
When Go 1.18 releases early next year, it will include the equivalent of:
typeany=interface{}
It seems like it would be great to update our code and examples to replace interface{} with any.
Create issues on HashiCorp maintained utility providers (as they may , if they are still using this framework
Since this framework must remain compatible with Go 1.17 until Go 1.19 is released later next year due to our compatibility promises, this codebase should not be updated yet.
bflad
changed the title
Consider Updating Code Documentation for Go 1.18 any -> interface{} Alias
Consider Updating Code and Documentation for Go 1.18 any -> interface{} Alias
Apr 14, 2022
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
SDK version
Use-cases
This framework generally requires heavy usage of empty interface types (
interface{}
,[]interface{}
,map[string]interface{}
) when working withhelper/schema.ResourceData
. This syntax is a little verbose and is not intuitive for newer provider developers or Gophers coming from projects which typically use concrete types.When Go 1.18 releases early next year, it will include the equivalent of:
It seems like it would be great to update our code and examples to replace
interface{}
withany
.Proposal
After Go 1.18 is released:
Since this framework must remain compatible with Go 1.17 until Go 1.19 is released later next year due to our compatibility promises, this codebase should not be updated yet.
References
The text was updated successfully, but these errors were encountered: