| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2024-03-01 | perf(cli): use new deno_core timers (#22569) | Matt Mastracci | |
| Improves #19100 Fixes #20356 Replaces #20428 Changes made in deno_core to support this: - [x] Errors must be handled in setTimeout callbacks - [x] Microtask ordering is not-quite-right - [x] Timer cancellation must be checked right before dispatch - [x] Timer sanitizer - [x] Move high-res timer to deno_core - [x] Timers need opcall tracing | |||
| 2024-01-01 | chore: update copyright to 2024 (#21753) | David Sherret | |
| 2023-07-13 | chore: update to Rust 1.71 (#19822) | Matt Mastracci | |
| 2023-05-17 | feat(ext/web): Request higher-resolution timer on Windows if user requests ↵ | Matt Mastracci | |
| setTimeout w/short delay (#19149) If a timer is requested with <=100ms resolution, request the high-res timer. Since the default Windows timer period is 15ms, this means a 100ms timer could fire at 115ms (15% late). We assume that timers longer than 100ms are a reasonable cutoff here. The high-res timers on Windows are still limited. Unfortuntely this means that our shortest duration 4ms timers can still be 25% late, but without a more complex timer system or spinning on the clock itself, we're somewhat bounded by the OS' scheduler itself. | |||
 |
index : deno.git | |
| Unnamed repository; edit this file 'description' to name the repository. | User & |
| summaryrefslogtreecommitdiff |