Facundo Domínguez

The example passes verification in the latest LH if writing the operator in qualified form: ``` {-@ assume (A.=) :: ... @-} ```

I cannot get the reported panic with the latest `liquidhaskell`. But I get a different panic now: ``` $ cabal exec ghc -- -package liquidhaskell Test.hs ... **** LIQUID: ERROR...

Sheesh, `z` is brought into the scope of a local spec if used in the local function. For instance, the following passes verification. ```Haskell foo :: Int -> Int ->...

I think that bindings are in scope only if GHC doesn't consider them deadcode. This is because when we get to analyse the desugared program, GHC has already pruned unused...

Hello @amigalemming. It looks to me like Liquid Haskell should have rejected all flavors of `powerAssociative`. If `n` is `-1`, then `div n 2` doesn't decrease, nor does it go...

I created #2285 to deal with negative dividends. Regarding this issue, looks like it could be addressed by either documenting why the termination checker fails to verify `go`, or fixing...

This is likely a duplicate of #2200. I cannot reproduce this error but I can reproduce the one in #2200. @amigalemming, what version of `liquidhaskell` are you using? And if...

That could be possible. We need to agree whether the `.liquid` directories should be placed, e.g. next to the interface files by default, and whether the user needs to be...

Here are the locations of interface files. They are rather intricate because they depend on the compiler version, the architecture, and the package they belong too. ``` dist-newstyle/build/x86_64-linux/ghc-9.8.1/liquid-prelude-0.9.2.8.1/build/Language/Haskell/Liquid/List.hi liquid-prelude/.stack-work/dist/x86_64-linux-nix/ghc-9.8.1/build/Language/Haskell/Liquid/List.hi ```...

I would expect ``` cabal exec ghc -- -plugin=LiquidHaskell Test.hs ``` to output `.liquid` in the current working directory (`./.liquid`), and ``` cabal exec ghc -- -hidir=output-folder -plugin=LiquidHaskell Test.hs ```...