Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update Prefer statically building constants.md #666

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Update Prefer statically building constants.md #666

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c524b5a
Update Prefer statically building constants.md
peter-mlabs Apr 10, 2024
c3e937e
Update Prefer statically building constants.md
peter-mlabs Apr 10, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions plutarch-docs/Tricks/Prefer statically building constants.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,16 @@ viacon = let currSym = pcon $ PCurrencySymbol $ phexByteStr "f1e301"

The semantics are both are the same. But the former (`pconstant`) compiles to a constant term directly. Whereas the latter compiles to some code that _builds_ the constant during Plutus Core runtime.

To better visualize this, we can look at the generated UPLC for `viaconstant` compared to `viacon`:

```
ghci> fromRight' $ Plutarch.compile (Config NoTracing) viaconstant
Script {unScript = Program {_progAnn = (), _progVer = Version {_versionMajor = 1, _versionMinor = 0, _versionPatch = 0}, _progTerm = Constant () (Some (ValueOf DefaultUniData (Constr 0 [B "\241\227\SOH"])))}}

ghci> fromRight' $ Plutarch.compile (Config NoTracing) viacon
Script {unScript = Program {_progAnn = (), _progVer = Version {_versionMajor = 1, _versionMinor = 0, _versionPatch = 0}, _progTerm = Apply () (Apply () (Builtin () ConstrData) (Constant () (Some (ValueOf DefaultUniInteger 0)))) (Apply () (Apply () (Force () (Builtin () MkCons)) (Apply () (Builtin () BData) (Constant () (Some (ValueOf DefaultUniByteString "\241\227\SOH"))))) (Constant () (Some (ValueOf (DefaultUniApply DefaultUniProtoList DefaultUniData) []))))}}
```

> Aside: Remember that Haskell runtime is actually compile-time for Plutarch! Even if you have a dynamically computed variable in the Haskell world, it's still a _constant_ in the Plutarch world. So you can use it just as well as an argument to `pconstant`!

Whenever you need to build a Plutarch term of type `a`, from a Haskell value, use `pconstant`. Whenever you need to build a Plutarch term of type `PAsData a`, use `pconstantData`!