On Sat, Sep 16, 2023 at 6:29 AM Ken Micklas <
kmic...@gmail.com> wrote:
>
> I have a use case for gccgo, but before investing in it more, would like to understand better the long term maintenance prospects. Currently it looks like gccgo has been stuck on basically Go 1.18 standard library features for a while, due to the lack of generics support in the frontend. Generics are not critical for my use case, but they make it challenging to use third party libraries from the ecosystem, and this seems like it might get worse over time.
>
> My understanding is that gccgo is always going to lag behind gc some amount, but that the goal is to still keep it maintained and eventually backport all language / standard library features from gc. Is that correct? If so, is there a very rough ETA for generics support?