christianschmitz
christianschmitz
Same as issue #4705 I fear that too many existing libraries and scripts now depend on TxId being serialized as ConstrData. So probably best to use `data TxId` instead of...
I noticed something similar with two much simpler scripts: the AlwaysFails and AlwaysSucceeds scripts in the [chris-moreton/plutus-scripts](https://github.com/chris-moreton/plutus-scripts) repo. AlwaysSucceeds seems to decompile into: ``` (program 1.0.0 [[(Λ (Λ (Λ (Λ...
Nice work! Looks like a pretty major rewrite. All inconsistencies I mentioned have been resolved, and once the encoding of `data` has been elaborated this issue can probably be closed....
I noticed something else: The first tag of the `Data` type on the bottom of page 17 reads `Constr Integer [Data]`: so second argument is a list of `Data` (presumably...
Table 3, page 19: How exactly does `mkCons` fail? (`consByteString` doesn't fail for example).
Ok, I thought that might be why `mkCons` can fail. Follow-up questions: * Does `ifThenElse` throw a *type error* if its branches don't have the same type? * I guess...
Page 21, note 3, second bullet point: now the condition is `c_i == d_i`, should it be `c_i
I've been using the Plutus-Core spec to develop an alternative smart contract DSL (https://github.com/Hyperion-BT/Helios/tree/dev). AlwaysSucceeds in the DSL is: ``` func main() -> Bool { true } ``` Which compiles...
Seems fair. The documentation has come a long way. The .tex file will be made part of the repository at some point? Will close the issue now. Good job, thanks!
We've considered implementing aggressive inlining for Helios when generating UPLC, if however the size of the reference script gets an associated cost at some point in the future this optimization...