This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-08-07
Channels
- # announcements (10)
- # babashka (39)
- # beginners (230)
- # calva (16)
- # cider (20)
- # clara (4)
- # cljs-dev (16)
- # clojure (35)
- # clojure-europe (8)
- # clojure-filipino (5)
- # clojure-france (1)
- # clojure-nl (6)
- # clojure-uk (9)
- # clojuredesign-podcast (1)
- # clojurescript (55)
- # clojurewerkz (1)
- # core-async (13)
- # cursive (1)
- # data-science (1)
- # datomic (4)
- # events (1)
- # fulcro (26)
- # jobs-discuss (1)
- # kaocha (3)
- # malli (53)
- # observability (9)
- # off-topic (1)
- # project-updates (1)
- # re-frame (15)
- # reagent (1)
- # reitit (11)
- # rum (8)
- # sci (29)
- # shadow-cljs (7)
- # vim (12)
- # xtdb (13)
@mfikes I'm actually surprised it ever worked - since setTimeout isn't a generally available thing
I think we should probably modify that test to only run if it's present since I believe it's a hard requirement?
Ahh, yeah... that seems like a decent argument... it is depending on something not guaranteed.
To be honest, I tried to find what setTimeout
is supposed to return... it is hard to find a real spec.
@mfikes setTimeout
is supposed to return a number identifying the timeout which you may then use via clearTimeout(theNum)
to cancel it. not sure if number is actually part of a spec but any kind of opaque value would do the same job, just not undefined 😛
Right... if you look at what Node does, it doesn't return a number. But given that, I went to see if I can find a spec that says that the result will be not undefined, and found it challenging. I suspect that this JSC build may have setTimeout
(unless David's comments above regarding exists?
lead to something), but that its implementation is botched.
@mfikes oh I think I misunderstood that detail - that setTimeout exists but that doesn't return the usual value
Yeah... my last comment in the ticket was only about distinguishing whether it is returning null
or undefined
.