Replies: 2 comments 1 reply
-
I'm happy to accept a PR for the iterator solution, as long as it does not break existing usages. That written: My gut feeling tells me that this is likely not possible due to conflicting trait impls. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Added PR for tuple of slices impl: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I authored stack-queue specifically so that I could create a data loader that integrates with Diesel. The current design only batches contiguous slices and simply starts a new batch whenever a task batch would otherwise wrap around to the beginning, however I could make this support wrap-around batching by returning an ordered pair of slices instead. The only way I could make this work and still integrate with BelongingToDsl without creating an intermediary Vec would be for BelongingToDsl to impl<'a, Parent, Child> BelongingToDsl<(&'a [Parent], &'a [Parent])> for Child
Alternatively this could work with an iterator over &Parent
Beta Was this translation helpful? Give feedback.
All reactions