I was excited to see the introduction to modern Haskell as I find that it's very confusing to enter Haskell these days as many or most introductions doesn't actually match current practices (Text vs. String, cabal vs. plain GHC, etc). However, I was bewildered when the Cabal & Stack section didn't mention Stack. Is this merely waiting for someone to write it? At the very least, we should be

At the moment our issues are a mess, and not very well categorised. We should probably adopt a labelling scheme like Rust's!

Plasma has a nice labelling scheme with a 'skill' label. This might help folks find something that they can help out with!

We have a reasonably good test suite with a lot of unit tests and a few test programs. It's very helpful and I use it all the time. But sadly, there are many cases that are not covered by the test suite. We can make it even more helpful! It'd be wonderful if people wanted to help out with this. It's also a very easy way to help out this project. I'm happy to assist anyone who wants to make a contr

We should parse markdown in the documentation comments, and produce the appropriate markup in the documentation based on that. pulldown-cmark could be useful for this.

It's unclear yet whether this should be implemented in Typology module itself, or TypologyLSP module. I'm inclined to do the former, as this would allow to do semantic checks against doc comments (number of parameters and their names) and make doc comment auto-complete suggestions with parameter names auto-filled.

At first glance this project seems to be quite similar to sanctuary-def. A summary of the differences between the two libraries would be useful. :)