Emily Pillmore
Emily Pillmore
I managed to reproduce this by modifying the `verifyCommand` code to output the cmd payload and aeson-parsed code in sequence using a minimal test command with test data ```haskell λ>...
I ran the above snipped and it was fine: ```lisp pact> (load "foo.pact") "Loading foo.pact..." "Loaded module ĞğŞşİı, hash _41-o9Bn38oK5DA1QALy3C7W_UKAzLCr1P8E5VKJKtQ" pact> (use ĞğŞşİı) "Using ĞğŞşİı" pact> (abŞ 3) 3 pact>...
Further updates: I've tracked down the cause of us receiving "empty" on bad input at runtime, and it's a subtle behavior of `msum` in the expression parser. We parse code...
@ptkato mind fixing? Since we never really infer cabal version, this would be a validation pass on the flag input in the driver.
Cheers! Thanks @roberth and @gbaz
> I proposed another approach: why not say good bye to the .cabal file format and switch to something that is widely supported. When I think about it, don't think...
@fendor Tzeenshe no longer works in Haskell, and has iceboxed the project until further notice
@djspiewak I wrote these down in the headers to the modules and in the README for that package: #### Can: `Can` is a pointed product. This means it's a discrete...
Gargantuan effort thank you! :smile:
If cabal-docspec breaks, i'll pick it up i suppose.