Allow external functions returning values #140
Merged
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.
So far an external function could not return any value (more precisely, return values were actually ignored, and 3D type-checked an external function call as returning
uniteven if the user stated a non-void return type in the declaration of the external function.)This PR fixes that issue, by:
unitreturn type in theextern_actioncombinator in the preludeWith this PR, an action can, for instance, call an external function and decide to succeed or fail depending on its return value. (This was long due; until now, one had to use out-parameters to painfully mimic this behavior.)
It also: