feat(data-structures/unstable): align RollingCounter with other data structures, add at() and toArray()

[tomas-zijdemans]

This PR is mostly about aligning RollingCounter with Deque, IndexedHeap, MultiMap and other data-structures.

• RollingCounter now implements Iterable.
• [Symbol.toStringTag] is a readonly "RollingCounter" as const property (was a getter).
• @experimental tag added to every public-member JSDoc.
• Class JSDoc gained a complexity table.
• New at(index) with Array.prototype.at semantics (oldest→newest, negatives from newest end, out-of-range → undefined).
• New toArray(); toJSON() delegates to it.
• RollingCounterSnapshot.segments is readonly number[]; field is readonly.
• from() accepts RollingCounterSnapshot, guards null/undefined/non-object, throws TypeError for shape errors, keeps RangeError for per-element numeric errors.
• Tests: two RangeError cases flipped to TypeError; added null/undefined snapshot, toArray, and at tests.

[codecov]

Codecov Report

❌ Patch coverage is 96.96970% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 94.61%. Comparing base (a496da2) to head (46f73eb).

Files with missing lines	Patch %	Lines
data_structures/unstable_rolling_counter.ts	96.96%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7102      +/-   ##
==========================================
- Coverage   94.61%   94.61%   -0.01%     
==========================================
  Files         634      634              
  Lines       51801    51818      +17     
  Branches     9329     9336       +7     
==========================================
+ Hits        49011    49027      +16     
  Misses       2216     2216              
- Partials      574      575       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[bartlomieju]

Overall solid PR. The new at() and toArray() methods are well-implemented, and the alignment changes (Iterable, readonly snapshot, @experimental tags, complexity table, Symbol.toStringTag as property) are all consistent with how Deque and other data structures work in this repo. Tests are thorough.

Two things:

1. Empty segments should throw RangeError, not TypeError

An empty array is the correct type — it's just the wrong length. The constructor throws RangeError for the equivalent constraint (segmentCount < 1), so from() should do the same for consistency. The other two TypeError changes (null/non-object snapshot, non-array segments) are correct.

2. PR scope vs title

The title says "add at() and toArray()" but the PR also changes the snapshot interface to readonly, adds implements Iterable<number>, switches Symbol.toStringTag to a readonly property, adds @experimental to all members, adds the complexity table, and reworks from() validation. The description documents all of this, but the commit message will be misleading in git log. Worth updating the title/commit message to something broader like "align RollingCounter with other data structures, add at() and toArray()".

[tomas-zijdemans]

Thanks,

• PR title and commit message changed as requested
• Changed from TypeError to RangeError as requested

[lunadogbot]

Author addressed both points from the prior review: from() now throws RangeError for empty segments (consistent with the constructor) and keeps TypeError for null/non-object snapshots and non-array segments; title is broadened to match the actual scope. The readonly [Symbol.toStringTag] = "Foo" as const field matches the pattern used by Deque, IndexedHeap, and MultiMap, so the getter → field switch is alignment, not drift. at() is a constant-time read off the ring buffer (segments[(cursor + 1 + index) % len]) with the canonical Array-style negative-index handling, and toArray() is the existing toJSON() body factored out — toJSON() correctly delegates to it.

• nit: at(1.5) returns undefined rather than at(1) because the fractional index leaks into the modulo. Array.prototype.at floors via ToIntegerOrInfinity first. Probably not worth coercing, but if you want strict parity, index = Math.trunc(index) at the top of the method would do it.

[lunadogbot]

@bartlomieju this is ready to merge