Alex Browne

@go-li thank you for reporting this issue. In this case, the compiler is behaving as intended (although I do want to improve the error message here by catching it earlier...

See #19. I don't think it's quite time for this. But I definitely will consider it in the future.

Thank you for sharing this. I have been following the discussion about generics in Go for years, but I did not know about some of these denser/summarizing documents. IMO it...

@go-li this looks really cool and thank you for letting me know about it :) See #2 for some background. Basically, my long-term plan for the importer is that it...

792cc6b8d84c8c3a1f6020faac4ce26e84decc76 gets us one step closer to this. It is now possible to import Go packages outside of the standard library. However, importing Fo packages is not yet supported. When...

I've been working a lot on this recently. The problem with my original plan is that it creates [cyclical imports](https://www.reddit.com/r/golang/comments/8qk6xw/fo_an_experimental_language_which_adds_generics/e0jzb2b/). So to work around this, I had to redesign the...

It might not be obvious, but the second playground link you shared shows an error coming from the Go compiler. Re-opening this because I would like the Fo compiler to...

I recognize that immutability is a core part of functional programming. However, I'm not sure how we could enforce this at the compiler level, especially given the existence of the...

@campoy I'm not sure what you are proposing exactly. Can you elaborate? How would this work with the existing slice type in Go?

Thanks @just1689 This is definitely something I'll be thinking about. Wanted to focus on getting the core language working first. For now, it usually works okay-ish to use Go syntax-highlighting....