effectfully
effectfully
Same as #4757 (at the time of writing). Just making sure I didn't screw up any git-related stuff.
### Summary Currently the unique of a variable is not pretty-printed with the default strategy, which I believe is in fact a bug, because parsing a pretty-printed program may get...
### Describe the feature you'd like Once #4738 gets merged, the classic syntax of builtins will look as follows: 1. built-in `Integer`: ``` (con integer) ``` 2. built-in `[Integer]`: ```...
This issue is for dumping all the plans regarding builtins in a largely unstructured way.
`concatMapM` has multiple problems. For one, it has a rather confusing name for a function defined like this: ```haskell concatMapM :: ( Applicative f , Monoid m , Container (l...
We use `tasty` with `cabal`'s internal libraries and some of our test suites depend on `tasty-golden` while others don't, so running `cabal test library-test --test-options "--accept"` fails with ``` Running...
The following snippet ```haskell putStrLn . renderString . layoutPretty defaultLayoutOptions $ pretty "a" mempty pretty "b" ``` gives this output: ``` a b ``` (two spaces between `a` and `b`)....
Having this ```haskell data D = C instance Eq D where C == C = True test = C ``` and trying to jump-to-definition of `C` results in both the...
This shows how to add a new way of costing an already existing builtin.
## Intro There exist multiple ways to create data types in Plutus Core: 1. Scott-encoding, long retired by now 2. sums-of-products (SOPs) 3. via the `Data` built-in type SOPs have...