Very interesting case. As Alex says, if you "help" the compiler writing the actual type parameter like `Append[Suiter](slice, suiter)` it works. I have seen this before in Java when generics comes into town... I guess with time golang team with time will improve the type inference engine... this also happens with typescript... perhaps is a common trait in evolution of language compilers.
Now if you allow me, I do appreciate that not using generics and using interfaces in your Append method things will work... I mean this <https://goplay.tools/snippet/GCxBeHMfipf>... I know... probably it won't fit to your coding issues... but what I feel sometimes is that generics aren't necessary and we tend to make use. I don't know.. forgive me if I'm wrong... just an opinion. El lunes, 23 de octubre de 2023 a las 0:01:47 UTC-3, tapi...@gmail.com escribió: > On Monday, October 23, 2023 at 10:38:59 AM UTC+8 tapi...@gmail.com wrote: > > Sorry, I didn't look your full code. > I think the full code should work with Go toolchain 1.21.n. > > > Aha, it actually doesn't. I'm surprised. > > > On Sunday, October 22, 2023 at 4:40:55 PM UTC+8 Mike Schinkel wrote: > > How so? > > Can you give an example scenario where it could cause unintended > consequences? Or some other negative? > > -Mike > > On Saturday, October 21, 2023 at 11:57:52 PM UTC-4 tapi...@gmail.com > wrote: > > > It is hard to call such type inference better. That is too aggressive. > > -- 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/f9ccf911-c7f7-4b68-bee6-26df2eb6eb1fn%40googlegroups.com.
