feat(Languages): Stateful Processes and Mech directory - #754
Open
fmontesi wants to merge 9 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds a first formalisation of Stateful Processes (for now without recursion), the textbook process calculus for reasoning about implementation of choreographies (syntactic descriptions of concurrent/distributed protocols). It includes both syntax and semantics of the calculus.
The semantics is split into symbolic (e.g.,
x := e; Pevolves toPby performing a transition with labelx := e) and concrete (which equips programs with memory and thus the same action would update variablexwith the value computed frome).One reason for this modularisation is future reuse: having a symbolic semantics is the basis to formulate extraction algorithms that infer the protocol executed by a network of process programs (choreography extraction in the literature). Another reason is that it is known to simplify some proofs of correctness for compilers from choreographies to processes, which is a future aim (see the README in
Mech).Choreographic languages will be part of future PRs.