Alex Browne

@go-li thank you for reporting this. ~~The issue lies with pointer dereference expressions of the form `*T` where `T` is a type parameter. After spending some time thinking about it,...

Related to https://github.com/albrow/fo/issues/27. Taking a closer look at your example: ``` func dontrunthisfunction[T](p *T){ dontrunthisfunction[*T](&p) } ``` Here, `*T` is a form of polymorphic recursion that will probably be disallowed...

I first started out by trying to use angled brackets since that is the syntax I was familiar with from other languages. I quickly found that it made the parser...

@ohir proposed using [special unicode characters](https://github.com/albrow/fo/issues/12#issue-332715476). I'm not in favor of this proposal because they are hard to type and can look too similar to other characters.

@maxekman I'm actually going to re-open this so that it is more obvious for anyone who wants to continue the discussion. I don't want people opening new issues for the...

@mandolyte asked on #26: > With the go2 generics proposal that is very close to your own experiments (except for the contract part), wondered if you were considering switching to...

@zenhack had this to say on #28 Syntactic ambiguity in generic type declarations: > This is another issue that was raised in the go 2 generics draft design, and was...

@zenhack thank you for opening this issue. I agree with your proposed solution to simply disallow this case. It should be easy enough to catch in the type checker.

Thanks for creating this issue. It's already something I'm planning to add and I don't expect it to be too difficult. Internally, the type-checker considers type parameters to have underlying...

Here's what I was referring to regarding type constraints and sum types. Suppose you have a generic add function: ``` func add[T](x, y T) T { return x + y...