Axel Wagner

Okay, using a clean fedora image works to reproduce the issue: ``` mero@vetinari ~$ sudo docker run -it fedora:latest /bin/bash [root@f0d3889f286b ~]# dnf install git vim golang [root@f0d3889f286b ~]# cd...

Hm… I'd like to ask you to reopen. Because 1. I already remove all `fedora` and `redhat` (and just to be sure just *all*) autocommands at the top of my...

@DeedleFake There won't be a "decision" on #49085 anytime soon. There are good reasons not to do it yet, but we also don't want to say it never happens. The...

> I can wait a bit longer. If a bad implementation goes in, I'll never get a good version. I think "a bit" is misleading. We are talking years -...

@DeedleFake The issue is not lack of understanding what a lack of parameterized methods means. It's just that, as @rsc said, wanting them doesn't make them feasible. The issue only...

> In terms of interactions with finalizers, the cleanup function will always run the first time the value pointed to by ptr becomes unreachable. That is, if an object has...

What does `Make((*T)(nil))` do? Useless and the answer is probably "return a `Pointer` that always returns `nil`", but just to make sure.

@ChrisHines You can't use the example as written, but you can use `sync.Map` with type-assertions instead. Or one of the third-party generic concurrency-safe map packages.

@CAFxX > When a module's go version is updated from a v1.Y < v1.X to a version v1.Z >= v1.X, a one-off migration is performed One note is, that there...

I don't believe you really addressed my point. The way I understand the proposal text, this code would break under your proposed migration: ```go var x int func TestA(t *testing.T)...