From 4c579728351899dbbe0d397d5bf801b112e2ad8e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?H=C3=A5kon=20Bogen?= Date: Tue, 5 Nov 2019 12:58:25 +0100 Subject: [PATCH] Fix broken link to episode (#35) --- 0079-effectful-state-management-wtp/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0079-effectful-state-management-wtp/README.md b/0079-effectful-state-management-wtp/README.md index d99c8b68..0e907e64 100644 --- a/0079-effectful-state-management-wtp/README.md +++ b/0079-effectful-state-management-wtp/README.md @@ -1,5 +1,5 @@ ## [Point-Free](https://www.pointfree.co) -> #### This directory contains code from Point-Free Episode: [Effectful State Management: What’s the Point?](https://www.pointfree.co/episodes/ep79-effectful-state-management-unidirectional-effects) +> #### This directory contains code from Point-Free Episode: [Effectful State Management: What’s the Point?](https://www.pointfree.co/episodes/ep79-effectful-state-management-the-point) > > We've got the basic story of side effects in our architecture, but the story is far from over. Turns out that even side effects themselves are composable. Base effect functionality can be extracted and shared, and complex effects can be broken down into simpler pieces.