<@U0FCV4RND> posted very good (subjective of cours...
# language-proposals
@Zac Sweers posted very good (subjective of course) abstract guide on keeping discussions productive that seems to be applicable to KEEP project https://gist.github.com/hzsweers/a2bb381aa184b353a383107c1739c964 Maybe we should add these rules ^ to KEEP's readme? ie PR about Type Classes seems to be suffering from the issues described in the guide. Nothing personal, but i don't really find code examples and discussion to be down-to-earth. In the end it's a compile-time ad hoc polymorphism that has different practical applications, but seems to be described too abstractly.