feat(collections): stabilize interleave#7115
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #7115 +/- ##
=======================================
Coverage 94.61% 94.61%
=======================================
Files 634 634
Lines 51801 51802 +1
Branches 9329 9329
=======================================
+ Hits 49011 49012 +1
Misses 2216 2216
Partials 574 574 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
bartlomieju
left a comment
There was a problem hiding this comment.
The change itself looks correct — rename, export updates, mod.ts re-export, @experimental removal all LGTM.
However, #7088 (which changed the signature from arrays to iterables) was merged just 5 days ago. I'd prefer to let the iterable-based API bake for a couple of weeks before stabilizing, since changing a stable API is much more costly if an issue comes up. Let's revisit this in mid-May.
lunadogbot
left a comment
There was a problem hiding this comment.
Matches the established stabilization pattern (e.g. fc259b0 Lazy, 3e91d1e debounce AbortSignal, fe0fb93 ServerSentEventParseStream): rename unstable_interleave.ts → interleave.ts, drop the @experimental tag, swap ./unstable-interleave for ./interleave in collections/deno.json, and re-export from mod.ts. Iterable input was locked in by #7088 (merged 2026-04-21), so the surface is stable. CI green on all matrix jobs.
|
@bartlomieju this is ready to merge |
The API was locked in here: #7088 so there should be nothing in the way of stabilization.
Note:
zipshould be updated to align withinterleave