[DNMY] Streamline Dispatch Variable Reference Structure #247
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
Codecov Report
@@ Coverage Diff @@
## master #247 +/- ##
=======================================
Coverage 99.81% 99.81%
=======================================
Files 33 33
Lines 7071 7071
=======================================
Hits 7058 7058
Misses 13 13
Continue to review full report at Codecov.
|
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 seeks to address #159. It turns out that dispatching on the index types accounts for a fair portion of the performance limitations: https://discourse.julialang.org/t/unexpected-allocations-with-multiple-dispatch/76988. Hence we have a balance between performance of expression creation (aided by
GeneralVariableRefs) and performance of querying values (aided by inhomogeneous datatypes). This PR seeks to find a good compromise.