The library documents itself · GUI & reactive
stzReactiveTask
13 own methods · 0 forms written with extensions, listed under their method
the source: base/reactive/stzReactiveTask.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
Then_
(no comment in the source: the name reads as a sentence) then_no extension
Catch_
(no comment in the source: the name reads as a sentence) catch_no extension
Execute
(no comment in the source: the name reads as a sentence) executeno extension
Status
The class recorded a status, a result and (now) an error, and offered no way to read any of them. A caller whose task failed could not ask what went wrong; a caller whose task succeeded could not collect the answer unless they had registered a handler first.no extension
Result
(no comment in the source: the name reads as a sentence) resultno extension
Error
"" when the task has not failed.no extension
HasFailed
(no comment in the source: the name reads as a sentence) has failedno extension
WasReported
Did the failure reach anyone -- a raise, a handler, or stdout? Only ERROR_IGNORE answers FALSE, and it is the one mode that asked to. Without this the fallback arm had no observable effect at all: removing it left every assertion green, because recording a reason is not reporting it.no extension
Succeeded
(no comment in the source: the name reads as a sentence) succeededno extension
Complete
Not every task computes. stzReactiveObject.SetAsync already HAS the value it is going to store, and its attempt to wrap one in a task function -- `func { return _newValue_ }` -- raised R24, because a Haro lambda cannot read a caller's local. These two let a caller that did the work itself still report it through the same task surface, so Status()/Result()/ Error() mean the same thing however the work happened.no extension
Fail
(no comment in the source: the name reads as a sentence) failno extension
Cleanup
(no comment in the source: the name reads as a sentence) cleanupno extension