Releases: Tfc538/timer_lib
Releases · Tfc538/timer_lib
v0.4.0
Full Changelog: v0.3.0...v0.4.0
v0.3.0
Changelog
All notable changes to this project will be documented here.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
[Unreleased]
None
[0.3.0] - 2026-03-10
Added
RecurringScheduleas the public recurring-timer configuration type.RecurringCadencewith fixed-delay and fixed-rate scheduling modes.
Changed
- Made recurring timer startup APIs schedule-based instead of interval-based.
- Moved recurring-only options like initial delay and expiration count onto
RecurringSchedule. - Updated tests, examples, and crate docs to reflect the new recurring API shape.
[0.2.1] - 2026-03-10
Added
- Recurring timer support for an explicit initial delay before the first tick.
- Per-callback timeout handling with dedicated timeout errors.
- Retry policy support for callback failures.
TimerRegistryhelpers for pausing and resuming tracked timers.TimerEventshelpers for waiting on paused, resumed, stopped, and cancelled transitions.
[0.2.0] - 2026-03-10
Added
TimerRegistryas the primary registry abstraction.- Graceful stop, immediate cancel, join outcomes, and lifecycle event streams.
- Lossless completion waiting via
TimerCompletion. - Builder-based timer startup with paused-start and event-control options.
- Stress, public API, weird-edge, and benchmark coverage.
Changed
- Raised the minimum resolved
bytesdependency to 1.11.1. - Reworked the runtime around explicit control commands and async-native internals.
- Made callback failures observable through outcomes, statistics, and event delivery.
- Removed manual
unsafe implusage from the timer and registry internals. - Updated the README, examples, and crate docs to match the current Tokio-based API.
v0.2.1
v0.2.0
- Introduces the async-native timer runtime redesign with TimerRegistry, TimerCompletion, graceful stop/cancel semantics, and builder-based startup.
- Adds broad verification coverage including public API, stress, weird-edge, doctest, and benchmark suites.
- Updates README, examples, and crate docs to match the current Tokio-based API.
- Raises the minimum resolved bytes dependency to 1.11.1.