[go-nuts] Block deprecated methods in git diffs
Go can’t break backwards compatibility, but we all know there are apis and features we wished were removed. What if go vet was extended to check if deprecated apis were used in the current git diff? Go can’t delete apis, but by extending go vet it can push back hard against their usage. It’s like a soft deletion. I would personally love for go to be able to start removing apis in this way. -- 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/A88E356C-7849-4223-B67D-CA2F348708B6%40gmail.com.
Re: [go-nuts] Re: Considering dropping GO386=387
Thank you! Ian Lance Taylor wrote: “On Fri, Jul 17, 2020 at 12:54 AM Hunter Herman wrote: > > Hi Austin! I’m very curious about the register based calling convention you > referenced in your email. Could you share more (informal is fine) details? See https://golang.org/issue/18597 and https://golang.org/issue/27539. 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/d0a3f82622f1a1a4631fdaecc4d36f23c7774236%40hey.com.
Re: [go-nuts] Re: Considering dropping GO386=387
Hi Austin! I’m very curious about the register based calling convention you referenced in your email. Could you share more (informal is fine) details? -- 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/8591e7ec-1418-4ac7-834d-93d1a00eb540o%40googlegroups.com.
[go-nuts] [generics] Awkwardness interfacing between primitives and structs
Suppose I want to write a function over any list like container (histogram, reverse...) how can I? Java requires special code if you want to process arrays — thus most code takes Lists, and accepting an array (eg a vararg) is likely to lead to a copy into a list at some point. Is go fated to inherit this sort of awkwardness? -- 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/5048-d7fa-4089-ab1a-ce0adbd80c20o%40googlegroups.com.
