902ceda8ad
Splitting out an independent refactoring to simplify #1865. There were many places in the code where we were pattern-matching on `ProcessedTerm` and/or `Module`, sometimes only to extract a single field, *e.g.* ``` ProcessedTerm (Module s _) _ _ <- maybeInitialCode ``` This was already getting a bit out of hand, and it also meant that any time we wanted to add an extra field to either `ProcessedTerm` or `Module` (as I will be doing in #1865), we would have to change every single such place in the code to add an extra wildcard pattern. This PR is a refactoring to 1. Derive lenses for all the fields of `ProcessedTerm` and `Module`, and 2. Prefer extracting named fields via lenses over pattern-matching in most places in the code. There were a few places in the code where we destructure a `ProcessedTerm` and use almost all the fields (e.g. when initializing a robot machine); I left those alone, first because extracting all the individual fields would be tedious, but more importantly because if we ever added any new fields in the future, it's likely we would actually want to use them in those contexts as well. |
||
|---|---|---|
| .github | ||
| .vscode | ||
| app | ||
| data | ||
| docs | ||
| editors | ||
| example | ||
| images | ||
| scripts | ||
| src | ||
| test | ||
| tournament | ||
| web | ||
| .gitignore | ||
| .hlint.yaml | ||
| .mergify.yml | ||
| .restyled.yaml | ||
| .stan.toml | ||
| cabal.haskell-ci | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| COMMUNITY.md | ||
| CONTRIBUTING.md | ||
| cspell.json | ||
| DESIGN.md | ||
| feedback.yaml | ||
| fourmolu.yaml | ||
| hie.cabal.yaml | ||
| hie.stack.yaml | ||
| LICENSE | ||
| NOTICE | ||
| pull_request_template.md | ||
| README.md | ||
| scenarios | ||
| stack.yaml | ||
| swarm.cabal | ||
Swarm
Swarm is a 2D programming and resource gathering game. Program your robots to explore the world and collect resources, which in turn allows you to build upgraded robots that can run more interesting and complex programs. More info can be found on the Swarm website.
Contributing
See CONTRIBUTING.md for information about various ways you can contribute to Swarm development!
Building
If you just want to play the game, head over to the Swarm website for installation instructions. If you want to build Swarm from source (e.g. in order to contribute, or to test out the latest bleeding-edge unreleased features), read on.
-
Clone the Swarm repository, e.g.
git clone https://github.com/swarm-game/swarm.git -
If you don't already have the
cabaltool:-
Get the
ghcuptool, a handy one-stop utility for managing all the different pieces of a Haskell toolchain. -
Use
ghcupto install a supported version of GHC:ghcup install ghc 9.6.4 -
Use
ghcupto installcabal:ghcup install cabal
-
-
Now use
cabalto build and run Swarm:cd /path/to/the/swarm/repo cabal run -O0 swarm:exe:swarm(Note that we recommend turning off optimizations with
-O0since they don't seem to make much difference to the speed of the resulting executable, but they make a big difference in compilation time.) -
Go get a snack while
cabaldownloads and builds all of Swarm's dependencies. -
You might also want to check out the
scriptsdirectory, which contains an assortment of useful scripts for developers.