haskell-mode VS eioio

You can use GHCI's debugger through Emacs's haskell-debug-mode (part of the haskell-mode package), and probably through other editor/IDEs as well, a programming editor like Emacs or Vim simply needs to be able to run a GHCI session and send commands to it.

No, I was only using haskell-mode. So I guess this is LSP's fault, then. Not Emacs's fault and not haskell-mode's fault.

If I made it sound like there's something like IntelliSense today, apologies! We've got <https://github.com/haskell/haskell-mode/blob/master/haskell-...>, but it's type-a-command-and-do-a-search: it's not linked in with completion directly in the setups I've seen.

(In practice, I'm usually starting from a slightly different place: I know I want a Frob and I've got a This and a That, so I do :hoogle This -> That -> Frob and get some options. The thought-process is working backwards from the goal more than forwards from one key object in focus. A different way of working, but I'm not convinced it's less effective.)

My point though was that it's an engineering issue, not a fundamental language limitation. ie not a reason all future languages should shun haskell features. The building blocks to do better at completion than haskell curently does are there.

check if you have any similar config to what caused this issue: https://github.com/haskell/haskell-mode/issues/1777 for me

Package-lint has been on my list, but the maintainer, MELPA's Steve Purcell, has been hesitant about NonGNU ELPA in the past (see this discussion), so I have skipped his packages for now, and also because most of the packages he maintains have a "broken" version tag, most of the time -- the reason here is that MELPA adds these manually, and since he understandably is targetting MELPA, there is little interest from his side to fix that.

You can see the expected output in this PR description.

I use haskell-mode. It has a shortcut for loading a module into REPL, and it also runs hasktags for me. That's literally all I use.

Just as a note from my poking around, this is the "official" way to use a nix-shell with haskell-mode: https://github.com/haskell/haskell-mode/blob/3a019e65b504861d7ea23afbfecd14e5ef63e846/haskell-customize.el#L77

the actual project (Readme has some code samples): https://github.com/ocaml-multicore/eio

For 5.0+ you might want to look at https://github.com/ocaml-multicore/eio for how effects can make async much more pleasant

Great post! I would love to see this extended to OCaml 5 (with eio) and Haskell

Second, effects enable a new style of concurrency libraries like eio that forgoes the need to wrap every asynchronous computation in a monad.

> This is realllly unidiomatic in real world Haskell.

Whether idiomatic or not does not matter. It proves my point:

IO won't save you, and even very mundane effects are not part of the game…

Idris is the "better Haskell" sure, but the effect tracking is still part of the uncanny valley (still IO monad based).

Koka is a toy, and Frank mostly "only a paper" (even there is some code out there).

The "Frank concept" is to some degree implemented in the Unison language, though:

https://www.unison-lang.org/learn/fundamentals/abilities/

Having a notion of co-effects (or however you please to call them) is imho actually much more important than talking about effects (as effects are in fact neither values nor types—something that all the IO kludges get wrong).

I think the first practicable approach in the mainstream about this topic will be what gets researched and developed for Scala. The main take away is that you need to look at things form the co-effects side first and foremost!

In case anybody is interested in what happens in Scala land in this regard:

https://www.slideshare.net/slideshow/embed_code/key/aLE9M37d...

https://docs.scala-lang.org/scala3/reference/experimental/cc...

But also the development in OCaml seems interesting:

https://github.com/ocaml-multicore/eio#design-note-capabilit...

Look mom, "effects", but without the monad headache!

To enable access to all these features, an exciting new library called Eio is being developed. It uses a new paradigm of direct-style concurrent I/O programming, without the need for monads or async/await, thus avoiding the function colour problem.