On Mon, Jul 20, 2020 at 1:23 AM Xie Zhenye <xiezhe...@gmail.com> wrote: > > Requiring type-information for parsing will brings difficulty for > implementing these tools, but not impossible. To solve ambiguity, the only > requiring type-information is wether a symbol is a type name or an > identifier. A parser package can help this.Since other languages like Java, > C#, TypeScript can solve this, it must be a way for Go.
I'm going to try to be very clear. Being able to parse Go without type information is a fundamental design decision of the language, made when the project started back in 2007 (before I joined the project myself). We are not going to change that decision. If the only way that we can add generics to Go is to require type information when parsing, then we will not add generics to Go. Fortunately the issue does not arise, as there are reasonable syntaxes that we can use for generics that do not require type information when parsing. Ian -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAOyqgcX82Cyjh6i3VR0KEG3ATAMTrpUxw8wFO4mCj7hB95P_uQ%40mail.gmail.com.
