Changkun Ou

I was trying to remove some of the `x := x` parts from my existing code. It turns out that [golangci-lint](https://github.com/golangci/golangci-lint) invokes go vet, and remains to report `loop variable...

According to the doc of [Write](https://github.com/golang-design/clipboard/blob/v0.7.0/clipboard.go#L134): Write writes a given buffer to the clipboard in a specified format. Write returned a receive-only channel can receive an empty struct as a...

Which clipboard receiver are you using on Windows? Are you using the system built-in clipboard? (On Windows, use Shift+Win+s) I remember from Windows; it might be problematic because there is...

removing Cgo on macOS is even more complicated than #25 There is a promising project https://github.com/ebitengine/purego but there is no clear practice on what should we do to remove the...

Good point. Is there any specific use case for 32-bit windows? I am 99% sure that this package didn't consider 32-bit windows.

Thanks for the investigation. As you already investigated the issue, any PR would be very welcome 👍

- Is `f[~T... any]` legal? - Is `kk := Keys{keys: ???}; for k := range kk.keys {...}` legal? - Is there an "unpack" to type params in this design?

> Note that F[~T any] isn't legal either. Sorry for the noise. I meant like this `f[T... ~int]`. Is it legal?

Just tried and I can reproduce the issue.

I don't think this is an issue with the frequent (but actually not) runGL call. An easy verification is to replace the big for loop inside runGL via `select{}`. As...