Phil de Joux
Phil de Joux
I noticed that riak dev setup uses other ports, eg. {http, [ {"127.0.0.1", 10018 } ]}, for dev1, 10028 for dev2
If someone looks at this, it might also be a good moment to consider whether we should be able to parse or pretty-print float values Infinity, -Infinity and NaN. ([comment](https://github.com/unisonweb/unison/blob/bf943e2df6b33acfcca549dfb8617d99e3988b35/parser-typechecker/src/Unison/TermPrinter.hs#L166))...
**Describe the bug** ``` > cd waspc > ./run stan ... stan: stan: panic! (the 'impossible' happened) (GHC version 8.10.7: readHieFile: hie file versions don't match for file: .hie/Wasp/Parser/Common.hie Expected...
If I run stan over the stack codebase it reports that is using all of the `.cabal` files, including those in test: ``` > stan report ... ⓘ Using the...
I couldn't locate src/test.agda so left that as-is.
The module comment in `Language.Haskell.Liquid.GHC.TypeRep` is truncated: https://github.com/ucsd-progsys/liquidhaskell/blob/c37ca0017f20070483ad0787e7f88f0223ac169a/src/Language/Haskell/Liquid/GHC/TypeRep.hs#L13-L22 It looks like the comment is a copy of a similar comment in `Language.Haskell.Liquid.GHC.Misc` but even that module doesn't heed the warning....
Similar to https://github.com/ucsd-progsys/liquid-fixpoint/issues/552, could we chip away at the hints found in `src/` maintaining an hlint gh-action and `.hlint.yaml` as we go? # Warnings currently triggered by your code -...
Could we spin the module Language.Haskell.Liquid.GHC.API off into its own package, such as `ghc-liquid`? I'm the author of [ghc-corroborate](https://hackage.haskell.org/package/ghc-corroborate) that does something similar but without [conditional coding with `CPP`](https://blockscope.com/posts/2022-02-23-iffy-diffy.html). We...
There are two failures reported with `stack test --fast`: ``` > git status On branch dev Your branch is up to date with 'origin/dev'. nothing to commit, working tree clean...