DateAPI that are not consistent across browsers and JS implementations are not exposed in a type-safe manner, you should access the underlying
jsObjectproperty if you need those.
This timer is an abstraction over
JSClosure.release()on it when the timer is deallocated. As a user, you have to hold a reference to a
JSTimerinstance for it to stay valid. The
JSTimerAPI is also intentionally trivial, the timer is started right away, and the only way to invalidate the timer is to bring the reference count of the
JSTimerinstance to zero. For invalidation you should either store the timer in an optional property and assign
nilto it, or deallocate the object that owns the timer.
JSObjectwrapper that enables throwing method calls capturing
Types conforming to this protocol can be constructed from