The library documents itself · GUI & reactive
stzReactiveFunc
3 own methods · 0 forms written with extensions, listed under their method
the source: base/reactive/stzReactiveFunc.ring(opens in a new tab) · All classes · The area reference: GUI & reactive
Under each method, its extensions (Q CS XT Z ZZ IB W U): bold and ticked, it exists; struck, it does not. The extensions and what they mean
No method of this class is run on this page: the class reaches files, the network, processes, the clock, chance or sound, and an example run here would only be an example of its effects. Each method carries the explanation the library gives of itself.
Method
Explanation, as the source carries it
Init
(no comment in the source: the name reads as a sentence) initno extension
Call_
AddTask is kept because CallAsync does the same and both are equally copy-bound; that is the engine-identity problem, not this method's, and papering over it here would hide it. Execute() on the LOCAL task is what makes the result real, which is exactly how CallAsync has always worked.no extension
CallAsync
CallAsync() for normal operations computations that should yield control to other operationsno extension