Skip to content
This repository has been archived by the owner on Sep 7, 2023. It is now read-only.

Support execution with transaction type-based dispatch #15

Closed
jeromesimeon opened this issue Feb 19, 2018 · 1 comment
Closed

Support execution with transaction type-based dispatch #15

jeromesimeon opened this issue Feb 19, 2018 · 1 comment
Assignees
Labels
Type: Feature Request 🛍️ New feature or request

Comments

@jeromesimeon
Copy link
Member

Currently, execution for clauses requires the user to specify the contract and clause. It would be useful to allow execution to be driven by the type of the incoming transaction (typically the clause request). The execution could match the incoming transaction type against the type signature of clauses.

This is also a useful item for integration with Cicero (#8), since Cicero already uses a form of dispatch.

@jeromesimeon jeromesimeon added the Type: Feature Request 🛍️ New feature or request label Feb 19, 2018
@jeromesimeon jeromesimeon self-assigned this Feb 19, 2018
@jeromesimeon
Copy link
Member Author

There is some initial dispatching logic supported now (switch expression over CTO class names). This is used when generating the execution logic for integration with Cicero.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Type: Feature Request 🛍️ New feature or request
Projects
No open projects
Development

No branches or pull requests

1 participant