Define core and sytems builtin functions - #109
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Establish that the Environment is a "fresh" slate of bindings inherited from the parent but otherwise empty, threaded through the evaluator but reset each time an invocation is made.
Plumb the machinery to supply Context to embedded functions so that domains can supply additional state and configuration to enable capabilities in their host environment to be accessed.
To this end a Domain trait is established, with definitions moved to the src/domain/ tree and then each domain able to supply a
functions()method in their implementation of that Trait.The linking phase now checks that all functions are resolved.
Finally this branch implements the
exec()function for executing shell scripts. This andnow()are available to all domains in a common "system" layer. This layer complements the pure builtins in "core", but in the future the common I/O functions could be ommitted by a domain if that were to be desirable.