Matthew Dempsky

Interesting. So strictly speaking, `string("foo")` and `[]string(nil)` do not meet the definition of "unnecessary" that unconvert uses: `"foo"` and `nil` are an untyped string and untyped nil, respectively, whereas the...

To confirm, are you using unconvert's -all flag?

I see. Unconvert should support your case with the -all flag. If not, that's definitely a bug. I'm not familiar with gometalinter though. I don't know how to have it...

The problem here is that when cross-compiling, the Go build system disables cgo support by default. When cgo is disabled, files that include `import "C"` are automatically omitted from the...

I added support at master for a `-configs` flag. Please take a look and let me know if it's helpful. Open questions: - Is JSON the best configuration format for...

> I.e. would it be possible to define an alias which tightens the constraints of the aliased type? Yes. `U` (type parameter with bound `comparable`) satisfies the constraint `any`, so...

@griesemer If we proceed with this proposal, I think it could be a nice convenience to keep `type A = B` as short-hand. But as it's not essential, I'd similarly...

> I don't see what the refactoring case is for changing the constraints of a type. Under this proposal, you can do more with parameterized type aliases than just change...

[re: value vs type domain analogies] I want to clarify that I made this analogy initially to help explain how I intuit the relationships here. Go's values and types operate...

> I think we have to consider what exactly an alias is in Go language: We're discussing amending the Go language spec here, so I think referring to the current...