swarm VS ghcid

Come join us at https://github.com/swarm-game/swarm/ ! We are very friendly and we have a bunch of small tasks suitable for beginners (see https://github.com/swarm-game/swarm/issues?q=is%3Aissue+is%3Aopen+label%3A%22C-Low+Hanging+Fruit%22) . No Slack or Discord but we do have an IRC channel and a Gather.town space (though it's not used very actively at the moment).

All the above listed projects are really great, worthy projects. But if you're looking for something a bit more frivolous, check out https://github.com/swarm-game/swarm/ .

https://github.com/swarm-game/swarm !

Check out Swarm if you like functional programming.

This is exactly what we do in swarm: https://github.com/swarm-game/swarm/blob/main/src/Swarm/TUI/List.hs If others are interested, we would be happy to collaborate to split this out into a separate library somehow.

Games that may fit are Screeps and Swarm (these are the two I know of, but there could be others in the same subgenre). The gameplay loop consists of you writing code to command your units who then go out to gather resources which you use to make better units and improve your base. Of course these types of games require you to do actual programming.

It's also great as a reference for PL implementors : https://github.com/swarm-game/swarm/blob/main/src/Swarm/Language/Typecheck.hs

Always happy to welcome contributors to https://github.com/byorgey/swarm (see CONTRIBUTING.md and issues tagged "low-hanging fruit" ). The needed level of expertise varies a lot from module to module, but there's a good deal that should be accessible to someone with a year of Haskell experience.

You can use ghcid. It compiles the code, and shows if there are any errors as you save your file. Have two terminals. One for editing your file...other one with ghcid ($ ghcid path/to/filename.hs). Right click on the ghcid terminal and click `always on top`. That way, It will be always visible as you are typing and saving code.

With a combination of ghcid, an hiedb filewatcher and the -fdefer-type-errors flag you can get pretty solid IDE behavior. Currently only ghc 9.4.4 is supported but happy to personally help people set this up if interested!

With an editor integration, you could rig it up to where you could right-click on a Spec, choose "Run spec" from a context menu, and have your editor add that comment to and save dev.hs. Another editor integration could read and parse the contents of ghcid.txt. We have this already for the compiler output, but it doesn't yet parse the test output. But sans an editor integration, you will still see the test output in the console where Ghcid is running.

Sounds like you want ghcid. You can use it run tests on a successful build, and it will watch files in your project and quick-rebuild when there are changes. There shouldn't be any need to modify your Cabal files or test dependencies.

In addition, for Haskell, I usually have ghcid running, which likewise re-runs on every file change, but gives faster feedback about any type errors than the full compiler, and also is configured to evaluate

Have you looked into ghcid? https://github.com/ndmitchell/ghcid

VS Code + Haskell extension is usually best, but ghcid is an alternative which is much simpler, easier to set up, less pretty and powerful but still pretty easy and effective to use. Here's a workflow:

In general, though, I recommend just looking at the cabal files for various libraries and executables. Something like ghcid is good, since it contains a library, an executable, and a test suite.

you should also checkout the ghci vim plugin https://github.com/ndmitchell/ghcid/tree/master/plugins/nvim