4 ms·
In response to this, I read the spec of setTimeout, bu I couldn't find the part where implementations may have an upper bound. Can someone more familiär with th
by n_plus_1_acc 2y ago
In response to this, I read the spec of setTimeout, bu I couldn't find the part where implementations may have an upper bound. Can someone more familiär with the specs point me in the right direction?
- zeven7 2y agoAdding a comment here to check back later because I'm curious now if someone has the answer. I thought it would be easy to find the answer, but I can't find it either. I figured it would say somewhere a number is converted to an int32, but instead I got to the part where there's a map of active timers[1] with the time stored as a double[2] without seeing a clear loss happening anywhere before that. [1] https://html.spec.whatwg.org/multipage/timers-and-user-prompts.html#map-of-active-timers https://html.spec.whatwg.org/multipage/timers-and-user-promp... [2] https://w3c.github.io/hr-time/#dom-domhighrestimestamp https://w3c.github.io/hr-time/#dom-domhighrestimestamp
- vilius 2y agoHere’s a deep dive in 6 minutes https://youtu.be/boD0ReK62FI?si=jSXuQn0DHn3riJgd https://youtu.be/boD0ReK62FI?si=jSXuQn0DHn3riJgd Just JS being JS: setTimeout(()=>{}, Infinity) executes immediately
- n_plus_1_acc 2y agoThanks, but I'm looking for the specification of this behaviour.