swarm/feedback.yaml

loops:
  build: cabal build -j -O0 --ghc-options='-Wall -Werror' all
  test: cabal test -j -O0 --test-show-details=direct swarm:swarm-integration swarm:swarm-unit
  unit: cabal test -j -O0 --test-show-details=direct swarm:swarm-unit
create feedback.yaml file For use with https://github.com/NorfairKing/feedback . 2022-03-19 19:08:35 +03:00			`loops:`
Don't set `it` variable when an exception was raised (#1922) Fixes #1899. It turned out the problem was not specifically with infinite loop detection but simply any time an exception was thrown and bubbled up to the top level. After logging the exception the CESK machine returned `VUnit` and there was no way for the UI to tell the difference between a computation that ended successfully with value `VUnit` and one with an uncaught exception. This PR adds a new special value `VExc` to denote the result of a computation that threw an exception. The UI can then check for this and not set the `it` variable in that case. 2024-06-10 22:14:45 +03:00			`build: cabal build -j -O0 --ghc-options='-Wall -Werror' all`
Recommend `cabal` (#1822) Changes to documentation etc. to recommend the use of `cabal` rather than `stack`. Closes #1820. - [x] Update `README.md` - [x] Update `feedback.yaml` - [x] Update scripts in `scripts/` - [x] Update `CONTRIBUTING.md` - [x] Maybe HLS defaults to using Stack now? Should we create a `hie.yaml.cabal` file with `cradle: cabal:`? - See https://discourse.haskell.org/t/whats-the-current-status-of-hls-cradle-discovery/8254/5 - See https://github.com/Avi-D-coder/implicit-hie 2024-05-06 03:09:33 +03:00			`test: cabal test -j -O0 --test-show-details=direct swarm:swarm-integration swarm:swarm-unit`
Parse comments (#1838) Towards #1467. This is incomplete but I thought it would be useful to split up the work into multiple PRs to avoid having a really massive one at the end. This PR accomplishes a few things: - Creates a new data type `Comment` to record the text of a comment, along with a bit of metadata giving its source location, whether it is a line or block comment, and whether it was on a line by itself or at the end of a line with some other non-comment tokens (this information will be used to decide which AST node to associate the comment with). - Adds a field to store comments in every `Syntax'` node. Note this is currently unused, since we haven't yet implemented the logic to insert comments into appropriate AST nodes (that will come in a later PR). - Note it's a bit annoying that the number of fields of each `Syntax'` node is growing. I did look into consolidating and generalizing `Syntax'` to just have a single field for arbitrary annotations, but the changes required seemed annoying enough that I didn't want to bother. 2024-05-12 03:32:21 +03:00			`unit: cabal test -j -O0 --test-show-details=direct swarm:swarm-unit`