You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 7, 2023. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: