From 35e2b90ba65176ae2fce6c109c28ab5bbe7e1fe9 Mon Sep 17 00:00:00 2001 From: Hayleigh Thompson Date: Sun, 31 Mar 2024 16:11:31 +0100 Subject: =?UTF-8?q?=F0=9F=94=80=20Create=20a=20guide=20on=20using=20and=20?= =?UTF-8?q?creating=20side=20effects.=20(#93)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * :memo: Explain why managed effects are useful. * :memo: Write a short explainer on pure functions. * :memo: Finish side effects guide. * :wrench: Add side effects guide to generated pages. --- examples/05-http-requests/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'examples/05-http-requests/README.md') diff --git a/examples/05-http-requests/README.md b/examples/05-http-requests/README.md index 4a118e4..c5fe073 100644 --- a/examples/05-http-requests/README.md +++ b/examples/05-http-requests/README.md @@ -51,8 +51,8 @@ want the Lustre runtime to execute before the next invocation of the `view` function. > **Note**: notice how the type of `view` remains the same. In Lustre, your `view` -> is always a [_pure function_](https://en.wikipedia.org/wiki/Pure_function) that -> takes a model and returns the UI to be rendered: we never perform side effects +> is always a [_pure function_](https://github.com/lustre-labs/lustre/blob/main/pages/hints/pure-functions.md) +> that takes a model and returns the UI to be rendered: we never perform side effects > in the `view` function itself. ## HTTP requests as side effects -- cgit v1.2.3