Optimize <|>:
implementation of Tabulation
#178
Merged
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.
Tabulation
has an instance ofAltTable
, which is intended to uphold the following law:The previous implementation was not actually defined in terms of
Query
's<|>:
(i.e.,UNION ALL
), because not everyTabulation
can be safelytoQuery
'd. Instead it used a combination ofalignWith
,catNonEmptyTable
andsome
that worked even on "magic"Tabulation
s.However, using
unsafePeekQuery
, we can actually "statically" determine if aTabulation
is "magic" or not, which means we can selectively switch the implementation to useQuery
's<|>:
where possible. This produces a simpler and usually faster query.