Ziyang Liu
Ziyang Liu
Reported by @jneira. For instance, `x = ({- comment -}1)` becomes `x ={- comment -} 1`, but it should be `x = {- comment -}1`. See https://github.com/mpickering/apply-refact/pull/101#issuecomment-760643564
There doesn't seem to be an easy way to tell which commit should be used for which GHC version. It would be helpful to add some tags for that purpose.
Copied from plutus-apps.
I added some builtin show functions, and followed the steps in CostModelGeneration.md up to step 8. Please check if everything looks good before I start running the benchmarks. In particular...
These modules aren't re-compiled if we modify, say, `PlutusIR.Transform.Beta`. But they should, because the plugin depends on it. Alternatively we can change the plugin to `impurePlugin`, but that seems like...
When using `nix-pre-commit-hooks`, `/nix/store/...python3.9-pre-commit-2.17.0/bin` is added to the end of PATH, possibly by [this](https://github.com/cachix/pre-commit-hooks.nix/blob/521a524771a8e93caddaa0ac1d67d03766a8b0b3/modules/pre-commit.nix#L322). This causes the wrong `pre-commit` to be used if you already have one in, say, `$HOME/.local/bin`.
I didn't see an existing issue on this - thought it would be a good idea to create one. This would enable apply-refact and other libraries depending on ghc-exactprint to...
When refactoring ```haskell f = \x -> case scrut of pat -> body ``` initially the `annEntryDelta` of `pat` is relative to the starting position of "case", in this case...
This is probably not the proper fix, but it does fix the problem I'm having. As far as I can tell, `ValidateAll / ValidateNone / ValidateSuchThat` were originally used to...