Internal changes to prepare for refactor #108
Merged
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
Pull in RC of numba so we can build docs on 3.12
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 PR should result in mostly the same end-user behavior. It's goal is to prepare for a larger API breaking change, where functions and classes are no longer tied to a particular EGraph, but instead are automatically defined whenever they are used in an EGraph.
This also means we can get rid of the concept of "Modules" and simply use named rulesets exclusively for differing semantic behavior.
Since this is quite a large change, I opted to make this PR preserve the old API while getting the machinery in place to rework things easily.
It also adds one feature, now default arguments to functions will be upcasted if necessary.