hint VS reflex

Mueval is based on hint, which is in turn based on the ghc library.

Yeah, that project is pretty much at the bottom of my list, unfortunately. My top projects these days are mgmt, klister, recursion-schemes, and hint... And that's already too much!

You can try using hint (instead of ghci) though I'm not sure it has the breakpoint functionality.

Have you tried hint?

with haskell.nix, well, you've found the github issue, you need to put the apecs package in the right nix incantation.

But the use case for that is for using a Haskell program A to catch errors in that same Haskell program A. For your use case, using a Haskell program A to automatically grade a Haskell program B, I recommend using the hint library instead, as it allows you to load code from external source files, run tests on them, and manipulate the error messages produced by ghc. (full disclosure: I am the maintainer of that library)

I am thinking of giving hint the ability to evaluate TemplateHaskell expressions. It would indeed be quite difficult to write an interpreter for all of Haskell, so my plan is to use the Exp's Show instance to produce a program which constructs and then splices that Exp, e.g. $(pure (InfixE (Just (LitE (IntegerL 1))) (VarE GHC.Num.+) (Just (LitE (IntegerL 1))))) is a Haskell expression which is equivalent to 1 + 1, so I should be able to ask hint to evaluate that to get 2 without having to write my own Haskell interpreter.

Yes please! Right now all of my open-source projects (most notably hint and recursion-schemes) are about to drop into barely-updated mode, and while I knew this would happen and have been working towards finding co-maintainers, I am now realizing that it wasn't enough. I think such a website would definitely have helped, and I am hoping that once it launches, I'll be able to use it to find some co-maintainers to tide over my projects until I become available again.

hint's API takes a string, not an AST (I plan to fix this). Internally, hint delegates to the ghc library, which does expose a parser which you can use if you want. hint exists to provide a friendlier API than the ghc library for interpreting Haskell code, but it does not expose a friendlier API for parsing Haskell code.

There's other people around here who would like to know your opinion about these GUI frameworks! I haven't written a GUI in Rust personally, but my favorite GUI framework is not at all OOP: https://reflex-frp.org/

Not to be confused with Reflex, allowing web apps in pure Haskell: https://reflex-frp.org/

FRP solutions sound very attractive. But reflex seems to be stuck on the outdated GHCJS, and I haven't been able to get it to build. The newer JS output in GHC doesn't yet have DOM support. And even if I used one of those, figuring out how to interact with a LaTeX renderer might be tricky.

I only have experience using Reflex, which I regard as the main contender for FRP UI libraries in the Haskell sphere. It's got a flashy website, but I think the documentation is a bit disorganized -- it took a long time for me to figure out how to get going with the library (you find some pieces of knowledge scattered here and there, if you look hard enough). My plan was to learn it well enough to onboard other people, but I don't think I could convince anyone who hasn't already decided that they're gonna make UIs in Haskell no matter the required effort.

Once someone has spent a bunch of time with Haskell and sees the value, they will find Nix if it makes sense. Maybe they'll want to play with https://reflex-frp.org, or they'll discover they want a better way to package 3rd-party dependencies, or they start using NixOS and want to nix all the things, etc. etc. Or, maybe they'll never find a use for it, and that's okay.

Reflex natively supports iOS, along with Android, desktop and web. I would recommend it for functional reactive programming in Haskell: https://reflex-frp.org

It's been awhile since I've tried to get into Ubuntu Touch/Linux mobile development in earnest. I'm currently working on an app using the reflex framework that I hope to eventually target Android, iOS, Desktop, and Linux Mobile.

If you're talking about the current Elm approach, I'm not sure. Otherwise, the paper I linked to notes some of the FRP libraries that existed at the time, some of which are still supported today (like reactive-banana), and otherwise I'd suggest looking at reflex, mentioned in the first post in this thread. I don't think it existed at the time the Elm paper came out.