-
In Plutarch the general consensus is that we perform Eq by simply delegating to the underling PlutusData representation.
```haskell
instance PEq FooTrivial where
(#==) = \l r -> pdata l #== pda…
-
### Describe the feature you'd like
Currently, each projects need to write some property testing generator and shrinker on per-project biases, making testing not only more difficult but possibly mo…
-
Some items for Plutarch if someone can take a look at that (NOTE: I don't use `Data` anywhere in naming because everything is `Data`, and on that note, imo `Scott` should have been explicitly named no…
-
Assigned to @icelandjack
L-as updated
7 months ago
-
De Fluviis. It's recorded as Plutarch but it's 100% a Pseudo.
-
Add a common module that provides ScriptContext mock with specific characteristics, and use it from several *Specs.
Context: In several PRs before, including #424, we are "stealing" mock `ScriptCon…
-
The proofs can in hindsight be made much more elegant.
Performance also needs to be considered, everything that can be represented as an integer
should be an integer.
Many GADTs should be made int…
-
### Describe the feature you'd like
Currently, in Plutarch (and I assume same for PlutusTx), we're emulating let bindings `let x = y; z` as `(\x -> z) y`, but this has the cost of introducing then el…
-
# Scenario
Consider the following validator that passes if the parameter is an ada currency symbol:
```
validator :: ClosedTerm (PCurrencySymbol :--> PData :--> PData :--> PScriptContext :--> POpaq…
-
Manually specifying GitHub source in `cabal.project` complicates it, leads to dependency incompatibilities and prevents plutarch dependencies from being published on CHaP themselves.