New syntax #6
New syntax #6
Conversation
uncomputable
force-pushed
the
new-design
branch
2 times, most recently
from
cf69857 to
d61319a
Compare
|
|
||
| Simphony code is valid Rust code _(assuming that used types, functions and constants are imported)_. | ||
|
|
||
| Writing sum values as `Either<A, B>` instead of `A + B` might seem pointless or verbose. |
|
I like the direction this is going towards. What does the [dosn't work] mean in section titles, do other programs compile/translate with the current rust-simplicity master? |
doc/new-syntax.md
Outdated
|
|
||
| The list type `[A; N]` can hold up to `N` values of type `A` where `N` is a positive integer. | ||
|
|
||
| We need to know the list size at commit time, so `N` will be somewhat large. There will likely be parts of the list that are unpopulated at redeem time. The definition of `[A; N]` as nested option-pairs keeps the onchain footprint small, since the unpopulated parts don't contribute extra bits to the onchain encoding. |
There was a problem hiding this comment.
Honestly I'd be tempted to use the syntax List<A, N> rather than [A; N] to emphasize that this is something weird and not very array-like. In particular it has linear access time.
There was a problem hiding this comment.
List<A, N> might be for the best. Originally I called this type "arrays" which is where [A; N] comes from. However, the values of this type have different lengths up to a maximum, so I renamed the type to "list".
doc/new-syntax.md
Outdated
|
|
||
| Expression `jet_j` where `j` is the name of a jet with source type `()`. | ||
|
|
||
| Expression `jet_j e` where `j` is the name of a jet with source type other than `()`, and `e` is an expression. |
There was a problem hiding this comment.
Should we use jet_j(e) to make Rust programmers more comfortable?
There was a problem hiding this comment.
I will make it jet_j(e) where e = (e1, ..., eN) can be shortened to e1, ..., eN and e = () can be shorted to e = ε (empty string).
There was a problem hiding this comment.
Yeah, I think that's reasonable.
doc/new-syntax.md
Outdated
| }); | ||
| ``` | ||
|
|
||
| # Compute sum of array [DOESN'T WORK] |
There was a problem hiding this comment.
What does the [dosn't work] mean in section titles
This is a reminder for myself that my Simplicity translation of list iteration doesn't work. This document is about syntax, but I like to have syntax grounded in a translation that might work.
uncomputable
force-pushed
the
new-design
branch
6 times, most recently
from
13487b6 to
bc9fcf0
Compare
|
Let's finalize a minimum-viable Simphony syntax + semantics without loops. The documentation is pretty much finished. Feel free to comment. I will start modifying the code base. One open question is what |
|
@uncomputable I think scoping should affect the Similarly these names should be invisible before the let statement. |
|
We probably need to tweak the context in some subtle way to handle this (maybe just having a stack of contexts where } pops everything off since the last {? These braces shouldn't have anything to do with precedence -- only ( ) parens should. |
|
ACK bc9fcf0 other than the above comments. Note that I only skimmed some of the notation-heavy descriptions of the contexts and translations. We are missing lists and loops entirely. Should defer these to a followup PR as you say. |
e6bca9e Grammar: Add Boolean type (Christian Lewe) 44320ad Grammar: Add None | Some match patterns (Christian Lewe) a30e595 Example: Add match (Christian Lewe) c5fd65e Grammar: Add match expressions (Christian Lewe) 92d4ebb Grammar: Remove witness declarations (Christian Lewe) 31428f8 Parse: Add WitnessName struct (Christian Lewe) dbf7046 Parse: Add Identifier struct (Christian Lewe) c375e0b Grammar: Update function calls (Christian Lewe) a8c23c0 Example: Update OP_CAT (Christian Lewe) 53ff1e0 Parse: Bit strings (Christian Lewe) fd22e34 Parse: Byte strings (Christian Lewe) 5b510a4 Grammar: Update expressions (Christian Lewe) 59a2723 Grammar: Remove destruct_pair (Christian Lewe) 41c2649 Grammar: Update patterns (Christian Lewe) ad19b1c Grammar: Update types (Christian Lewe) 530f78f Parse: Assert rule types (Christian Lewe) e687ea2 Grammar: Add line comments (Christian Lewe) 0929716 Grammar: Update whitespace (Christian Lewe) 2396560 Cargo: Include rust-miniscript 11 (Christian Lewe) 536d60b Cargo: Use rust-simplicity 0.2.0 (Christian Lewe) Pull request description: Implementation of new syntax and semantics from #6: types, values, match statements, unwraps. The Simplicity compiler panics on every error, as on master. I will fix this in a follow-up PR. Types and patterns are parsed nonrecursively. Expressions are more complicated and are currently parsed recursively. There will be a follow-up PR. ACKs for top commit: apoelstra: utACK e6bca9e Tree-SHA512: 831ee92fd585183b468abe574b142eb78c6181f485aedff0acb70f4feb3389bdbb603720e828a9f8dc66739d314696fec40621bf32b514b14f190e0bf76274c6
No description provided.