OptionalscheduleFn: SchedulerFnIn addition to refreshing pending rules, this also updates "demand" changes for reactive functions with tasks, streams, and recalcWhen uses. That is, in addition to running any pending rules on the specific scheduler, it also subscribes to things that gained demand, and unsubscribes/cleans up things that lost demand.
This can cause thrashing (doing and undoing the same thing) if not used carefully, so again, try to reserve its use to either tests, or as the last action of a synchronous event handler with a response deadline.
Synchronously run any pending rules tied to a specific schedule.
(Note: "pending" rules are ones with at least one changed ancestor dependency; this doesn't mean they will actually do anything, since intermediate cached() function results might end up unchanged.)
You should normally only need to call this when you need to force side-effects to occur within a specific synchronous timeframe, e.g. if rules need to be able to cancel a synchronous event or continue an IndexedDB transaction. (Otherwise, this is really only useful for testing.)