haskell-language-server VS tilapia

The advent of language server protocol made possible the creation of HLS (Haskell Language Server), and there are plugins for many editors, such as vscode-haskell, that allow you to have auto-complete, auto-import, and automatic function signatures—also available to your editor of choice. The whole feedback loop of editing, compiling, and running is greatly improved.

HLS 2.3.0.0 is currently broken on Windows.

The Haskell community has been focusing on tooling and IDE support in the last several years. Haskell-Language-Server is a huge improvment, so the experience is probably much better than you remember, but it'll still be a while before it catches up with Rust.

static-ls is a low memory language server for Haskell that serves as an alternative to (hls)[https://github.com/haskell/haskell-language-server] with less functionality by using statically generated information. It is intended for (Highly recommend hls instead if you aren't having these issues):

I think the corresponding HLS PR is https://github.com/haskell/haskell-language-server/pull/3462, so it isn't landed yet but hopefully can be part of a HLS release before too long. (I'm not sure if it will make it in to the very next release because we're due one out to support GHC 9.6.1 pretty soon.)

Perhaps the documentation for Char should contain examples of how you write the literals. Tracking as https://github.com/tomjaguarpaw/tilapia/issues/128

Can you please report concrete examples here: https://github.com/tomjaguarpaw/tilapia/issues/new

I'll do what I can to improve the situation, but I need to know which packages precisely you are talking about.

Thanks! Tracking at https://github.com/tomjaguarpaw/tilapia/issues/109

It would be nice with a "modern cabal for stack users" tutorial (ddg tells me it's an issue https://github.com/tomjaguarpaw/tilapia/issues/11 ), answering questions like

If you're on Windows and you're feeling brave you could try these new instructions developed by a collaborator of mine over at the tilapia project. If anything goes wrong with those instructions then please put a message on the pull request describing what the problem was and we'll try to get it fixed.

Great! I'd be happy to have you on board. Please "Watch" the repo so that you are notified of discussions that happen there. Feel free to start your own discussions at any time by opening an issue.

Feel free to collaborate with me on Tilapia. At the very least I would welcome knowing about your ideas.

I also have a personal project (tilapia) for tracking difficulties in the Haskell ecosystem. Feel free to post any observations, questions or difficulties there.