Initial move to the V2Engine #38
Draft
Conversation
This file contains 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
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.
This is a PR to the "forloops" branch which is going to be the next Hudder version.
Recently I've copied the V2Runtime (which is the basis for the Hudder language) and made it it's own separate program called V2Engine. At the time this was a one time thing, but now I find myself needing the V2Engine for another project of mine in the works, but I don't want to maintain 2 different versions of the V2Runtime, one for Hudder and one for all my other projects.
The goal of this PR is to see if and how far I can make Hudder's version of the V2Runtime less dependent on Hudder and markup features in the hopes that one day I can use it's code for the V2Engine with 0 modifications.