Skip to content

join: name the shared key container to fix HRTB normalization#798

Merged
frankmcsherry merged 1 commit into
TimelyDataflow:master-nextfrom
frankmcsherry:join-named-key-container
Jul 14, 2026
Merged

join: name the shared key container to fix HRTB normalization#798
frankmcsherry merged 1 commit into
TimelyDataflow:master-nextfrom
frankmcsherry:join-named-key-container

Conversation

@frankmcsherry

Copy link
Copy Markdown
Member

Apply the same fix as the reduce commit to join_traces and Arranged::join_core. Both equated the second cursor's key to the first cursor's key projection (for<'a> Key<'a> = BatchKey<'a, Tr1>), a higher-ranked projection-to-projection bound that fails to normalize through a join wrapper generic over both inputs with a non-reference GAT key (columnar Ref), with the same error[E0271]: expected <_ as Cursor>::Key.

Name the shared key via a container parameter KC: pin it from the first input's KeyContainer and equate both cursor keys to KC::ReadItem. In join_core this sits alongside the existing Diff = R1/R2 pins, which solve the identical use-site-connection problem for the diff type.

Apply the same fix as the reduce commit to `join_traces` and
`Arranged::join_core`. Both equated the second cursor's key to the first
cursor's key projection (`for<'a> Key<'a> = BatchKey<'a, Tr1>`), a
higher-ranked projection-to-projection bound that fails to normalize through a
join wrapper generic over both inputs with a non-reference GAT key (columnar
`Ref`), with the same `error[E0271]: expected <_ as Cursor>::Key`.

Name the shared key via a container parameter `KC`: pin it from the first
input's `KeyContainer` and equate both cursor keys to `KC::ReadItem`. In
`join_core` this sits alongside the existing `Diff = R1/R2` pins, which solve
the identical use-site-connection problem for the diff type.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@frankmcsherry frankmcsherry merged commit 679f561 into TimelyDataflow:master-next Jul 14, 2026
6 checks passed
@github-actions github-actions Bot mentioned this pull request Jul 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant