Add rate limiter problem specifications #2588
Closed
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.
Summary
Details
Added: exercises/rate-limiter/canonical-data.json
Property: rateLimiter
Input: limit (int), windowMillis (int), operations (array)
Operations:
{"op":"allow","key":string} → produce a boolean in order
{"op":"advance","millis":int} → advance the simulated clock
Covers: within-window allowance, window reset, per-key independence, exact boundary semantics, multi-window behavior, and invalid configs (limit<=0, windowMillis<=0).
Added: exercises/rate-limiter/instructions.md
Describes fixed-window semantics, per-key counters, boundary handling, and a suggested API with an injectable TimeSource to avoid sleeps in tests.
Added: exercises/rate-limiter/introduction.md
Provides context and motivation for rate limiting.
Added: exercises/rate-limiter/metadata.toml
Title and blurb for track integration.
Rationale
Discussion Link: https://forum.exercism.org/t/new-exercise-proposal-rate-limit/19109