Try out TypeGroupedNamedTuple #3362
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
charleskawczynski
force-pushed
the
ck/try_type_grouped_named_tuple
branch
from
2b04d55
to
e2a88c3
Compare
charleskawczynski
force-pushed
the
ck/try_type_grouped_named_tuple
branch
from
e2a88c3
to
37980de
Compare
charleskawczynski
force-pushed
the
ck/try_type_grouped_named_tuple
branch
from
37980de
to
e85d503
Compare
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.
Since NamedTuple's contain type information for every variable and type, this can significantly increase our type space. One thought I had was to group our types, and then use
NTuples to reduce the type information. This PR tries out this idea, to see if/how this impacts compilation times.