(side-effects-optimizer state future-steps)The optimizer is risky, messy business. It is a chance to look forward into next few steps in the execution, and do something about them ahead of time. A possible optimization may be to carry out async side effects ahead of time, so their outcome is ready earlier. Yet another optimization is the batching of multiple side effects together, e.g. querying once rather than many times. The optimizer is expected to return a modified state, so whichever tactic used here, it must work through mutating the state.
The optimizer is risky, messy business. It is a chance to look forward into next few steps in the execution, and do something about them ahead of time. A possible optimization may be to carry out async side effects ahead of time, so their outcome is ready earlier. Yet another optimization is the batching of multiple side effects together, e.g. querying once rather than many times. The optimizer is expected to return a modified state, so whichever tactic used here, it must work through mutating the state.
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |