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
This is more of a design question. Should Clarity statically infer whether or not a define-public function is also read-only? I think this could be useful for the RESTful API -- you should be able to call a define-public function if it won't mutate any state.
The text was updated successfully, but these errors were encountered:
The answer is yes, we can do this, but more generally, we can run any functions (or eval any code we want) via the RESTful API, as long as we make it clear that no mutations will be materialized.
This is more of a design question. Should Clarity statically infer whether or not a
define-public
function is also read-only? I think this could be useful for the RESTful API -- you should be able to call adefine-public
function if it won't mutate any state.The text was updated successfully, but these errors were encountered: