The following excerpts from the "Concepts > Effect Handlers" page are really outdated, mentioning Console:
|
# An Introduction to (Algebraic) Effect Handlers |
|
Besides the built-in functions like `println` that have effects (e.g. `Console`), |
|
which are tracked by the effect system, Effekt also offers _user definable control effects_. |
... and the notion of "builtin effects"
|
> **Remark** |
|
> Builtin side-effects like printing to the console are tracked, but cannot |
|
> be handled, and their semantics is fixed. Hence, we do not track them as |
|
> effects, but as [second-class _resources_](https://doi.org/10.1145/3527320). |
For effect handlers in particular, it might be worth it to cross-reference them with the Tour: the page Tour > Captures has a nice explanation of captures, but the Concepts > Effect Handlers seem a better intro to handling than the Tour > Effect Handlers.
The following excerpts from the "Concepts > Effect Handlers" page are really outdated, mentioning
Console:effekt-website/docs/concepts/effect-handlers.md
Lines 7 to 9 in 8799da2
... and the notion of "builtin effects"
effekt-website/docs/concepts/effect-handlers.md
Lines 50 to 53 in 8799da2
For effect handlers in particular, it might be worth it to cross-reference them with the Tour: the page Tour > Captures has a nice explanation of captures, but the Concepts > Effect Handlers seem a better intro to handling than the Tour > Effect Handlers.