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.

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

Get rid of main {} #155

Open
fare opened this issue Aug 15, 2019 · 0 comments
Open

Get rid of main {} #155

fare opened this issue Aug 15, 2019 · 0 comments

Comments

@fare
Copy link
Contributor

fare commented Aug 15, 2019

In the long run, we want composable interactions, so that rock-paper-scissors can be the sub-interaction of something bigger. That means that describing interactions MUST NOT depend on a "main" block, but should be described in a function, and/or if a function is not enough, a "module" (in the style of OCaml and with the JavaScript-extending syntax of ReasonML) should encapsulate it.

The syntax issue is minor—the important part is understanding the semantic issue, how it enables composability of interactions, and how it affects their verification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant