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.
As mentioned in #4, we are no longer focusing on being a complete Scheme implementation, but taking advantage of the Lisp structure to simply be a DSL for writing abilities and thus only focusing on the necessary features for that use case:
I'd want to figure out how the API starts before committing to how it should operate.
This does mean we will rip out all interpreters in this repo (as we no longer execute anything...)
But that does mean we can move any structure dealing with abilities and how they are handled to this crate, which Magicflute being responsible for maintaining runtime representations for and executing the abilities described.
I'll leave the pre-dsl code in a separate branch b/c I might figure out and want to build out a full Scheme implementation in the future...