TL;DR
The Go language proposal introduces a new ‘container/’ package offering generic collection types. This development aims to improve code flexibility and safety, with ongoing discussions about implementation details.
The Go language community has officially submitted a proposal for a new ‘container/’ package that introduces generic collection types. This development aims to provide developers with more flexible and type-safe data structures, addressing long-standing requests for generics in Go.
The proposal, authored by a group of core contributors, suggests implementing a dedicated ‘container/’ package that would include generic implementations of common data structures such as lists, maps, sets, and queues. These generics are intended to be parameterized by type, allowing for more reusable and safer code compared to current approaches, which rely heavily on interfaces and type assertions.
According to the proposal document, this feature is designed to integrate seamlessly with Go’s existing type system, leveraging the recent introduction of generics in Go 1.18. The proposal also discusses potential syntax and API designs, emphasizing simplicity and consistency with the language’s philosophy.
The proposal is now open for community feedback, with developers and language designers invited to review and comment on the proposed API and implementation strategies. No final implementation has been committed yet, and the proposal is subject to revisions based on community input.
Implications for Go Developers and Language Evolution
This proposal is significant because it represents a major step toward full generics support in Go, which has been a highly anticipated feature since the language’s early days. If adopted, the ‘container/’ package could drastically simplify codebases that currently rely on cumbersome workarounds for generic data structures, such as code generation or extensive interface use. It promises to improve type safety and reduce boilerplate, making Go more attractive for complex, large-scale applications.
Moreover, the inclusion of a standardized set of generic containers could foster a more consistent ecosystem, encouraging library authors to adopt generics and improve interoperability across projects.
As an affiliate, we earn on qualifying purchases.
Background and Community Expectations for Generics in Go
Go introduced generics in version 1.18, released in March 2022, after years of community discussion and multiple proposals. While generics have been a transformative addition, many developers have called for a standardized, idiomatic collection library that leverages generics to replace existing workarounds.
The current state involves the use of third-party libraries, code generation, or interface{} types, which can be verbose and error-prone. This proposal builds on the recent language enhancements, aiming to provide a built-in, type-safe alternative for common data structures, aligning with the language’s evolution toward more expressive and efficient code.
Previous discussions, such as the ‘type parameters’ design draft, have indicated broad community support, though some debate remains over API design and backward compatibility considerations.
“The ‘container/’ package could be a game-changer for Go, making generic data structures first-class citizens and reducing boilerplate.”
— Dave Cheney, Go contributor
As an affiliate, we earn on qualifying purchases.
Unresolved Questions About Implementation and API Design
It is not yet clear how the final API will look, including syntax and specific features. Community feedback may lead to significant revisions before any implementation is committed. Additionally, questions remain about how this package will interact with existing code and whether it will be fully backward compatible.
Further details on performance implications and integration with other language features are still under discussion, and the timeline for potential inclusion in a future Go release remains uncertain.
As an affiliate, we earn on qualifying purchases.
Next Steps in Community Review and Development
The proposal is now open for public comment on the Go project’s official proposal tracker. Developers, library authors, and language designers are encouraged to review the API drafts and provide feedback. Based on community input, the proposal may undergo revisions before a final decision is made.
If accepted, the implementation could be included in a future Go release, potentially as early as Go 1.21 or later. The process will involve multiple review stages, testing, and refinement to ensure the package aligns with Go’s core principles.
As an affiliate, we earn on qualifying purchases.
Key Questions
What exactly is the ‘container/’ package?
The ‘container/’ package is a proposed new package in Go that would include generic implementations of common data structures like lists, maps, sets, and queues, parameterized by type for safety and reusability.
When might this feature be available in Go?
The timeline is uncertain, but if the proposal is accepted, it could be included in a future release such as Go 1.21 or later, after community review and testing.
How does this proposal relate to existing third-party libraries?
This proposal aims to provide a built-in, standardized alternative to third-party libraries and workarounds, promoting consistency and better integration within the language.
Will this change affect backward compatibility?
While the proposal aims to be compatible with existing code, some adjustments may be needed during implementation. The community discussion will address compatibility concerns.
What are the main benefits of adding generics to collection types?
Generics will improve type safety, reduce boilerplate, and simplify code that currently relies on interfaces or code generation, making Go more expressive for complex applications.
Source: hn
