/
Rholang requirements for Mercury
Rholang requirements for Mercury
All Typing is icing on the cake.
We should focus on everything else first.
Essential Features that are not currently implemented 2018-01-12
- Non-linear bindings.
- ... Tuple capture
- @ Destructuring and Process vs Name tracking. This is a very simple typing, and probably all we should promise for Mercury
- IOPairs → requires support in the tuplespace library.
- Arithmetic expressions need to act on arbritrary processes, not just quantities. (So that *x + *x will compile)
- Name unforgeability
Caveats
- We will not likely support destructuring of arbitrary processes, only values for mercury.
- We will support construction of arbitrary names. (If it comes to it, we could probably construct the names we need as values.)
When we do support process destructuring and matching, we will likely want to add an ```opaque { P }``` construction that won't destructure further.
Other requirements:
- Target library needs to be well documented.
, multiple selections available,
Related content
Mercury Documentation
Mercury Documentation
More like this
Rholang Interpreter
Rholang Interpreter
More like this
Interfacing Comms, Storage, and Rholang Meeting notes
Interfacing Comms, Storage, and Rholang Meeting notes
More like this
Rholang Sprint 5 Retrospective
Rholang Sprint 5 Retrospective
More like this
Project Planning Feb 8th, 2018
Project Planning Feb 8th, 2018
More like this
Project Planning May 16, 2018
Project Planning May 16, 2018
More like this