Docs for casing on constants #7481
Conversation
basetunnel
temporarily deployed
to
github-pages
GitHub Actions
Inactive
|
basetunnel
temporarily deployed
to
github-pages
GitHub Actions
Inactive
|
The doc seems useful! I propose to add Plinth examples to accompany UPLC examples, as this user guide is for Plinth and it makes sense to showcase its types/expressions too. |
zliu41
left a comment
zliu41
left a comment
There was a problem hiding this comment.
Our convention for docs is to put each sentence on one line. No need to update this one but please keep it in mind in the future.
| ## Compiling to `case` in Plinth | ||
|
|
||
| When compiling Plinth code with the [option](./plinth-compiler-options) | ||
| `datatypes=BuiltinCasing`, many standard library functions will be compiled into |
There was a problem hiding this comment.
We need to mention that this option is going away post hard fork (see the comment on the DatatypeStyle data type). Also please make an issue to update this post hard fork.
|
|
||
| ::: | ||
|
|
||
| In UPLC, it is possible to branch on expressions of certain built-in types, like |
There was a problem hiding this comment.
We should mention other ways of deconstructing builtin types (e.g., for bool one can use ifThenElse), and why using the new builtin casing feature is better.
| lam x (case x (lam a (lam b [(builtin addInteger) a b]))) | ||
| ``` | ||
|
|
||
| ### Integer |
There was a problem hiding this comment.
Mention that the datatypes=BuiltinCasing optoin is irrelevant to Integer. To take advantage of casing on integer, in Plinth one must use PlutusTx.Builtins.caseInteger.
No description provided.