Axel Wagner

@AaronFriel Note that the reason generic types are not part of `reflect` is that generic types don't exist in a valid Go program. For them to be represented in `reflect`,...

I ran two successive puts with debug verbosity, to see where the bottleneck is: ``` red@hix ~$ echo 'put -in=.zshrc [email protected]/foobar\nput -in=.zshrc [email protected]/foobar\n' | upspin -log debug shell 2017/12/07 20:18:14.263721...

I built the upspinserver binary from HEAD (b6cbee6f6dfe62ee7474db0dc25e0ed106cd4969), scp'ed it to /tmp and ran it with /tmp/upspinserver -addr jeremy.merovius.de:443 -https :443 -web -letscache /srv/upspin/letscache -serverconfig /srv/upspin/server/ -config /srv/upspin/server/serverconfig.json With that,...

Yes, I'm fine with the rename. In the meantime, I built my own Dockerfile to deploy and am using that. But eventually, having a working one from upstream that gets...

@wallyqs Ah that's fair. I observed the error in a test, where I was actually using `context.Background` and extrapolated from the error message and the docs of `FlushWithContext`. So, just...

Okay, great, it seems that it's only `FlushWithContext` then. And maybe the error message could be a bit more descriptive, if the issue is usage of `context.Background()`, not the lack...

FWIW, I deleted my scaleway account yesterday, as this doesn't seem to be happening.

Personally, I don't really see the need to make `range` work with defined types. I think iterators (like [sql.Rows](https://pkg.go.dev/database/sql#Rows)) produce well-readable, efficient code, without a language change (whereas the `Do`...

@leighmcculloch > I think in this case the rewritten function is captured which captures the scope of the function containing the for loop like it would if the user referenced...

@deanveloper ```go type Collection[Elem any] interface { Do(func(Elem) bool) } type mapper[T, U any] struct { c Collection[T] f func(T) U } func (m mapper[T, U]) Do(f func(U) bool) {...