diff options
| author | muqiuhan <[email protected]> | 2024-09-15 14:27:49 +0000 |
|---|---|---|
| committer | muqiuhan <[email protected]> | 2024-09-15 14:27:49 +0000 |
| commit | 6444baa72396ffa7ad26e59967c2dcd43c90877c (patch) | |
| tree | 1837db5a8ce4e067aa49459b03894c138310d201 /2024/09/12 | |
| parent | fc5691ec39cbd581b088c0ee1a6cb4a552decd28 (diff) | |
| download | blog-6444baa72396ffa7ad26e59967c2dcd43c90877c.tar.gz | |
deploy: 838f92a9b62d46d4ec5e00c896896255ddcdf7ab
Diffstat (limited to '2024/09/12')
| -rw-r--r-- | 2024/09/12/Functional-Reactive-Programming-in-F/index.html | 16 |
1 files changed, 15 insertions, 1 deletions
diff --git a/2024/09/12/Functional-Reactive-Programming-in-F/index.html b/2024/09/12/Functional-Reactive-Programming-in-F/index.html index dd82f7a2..301be807 100644 --- a/2024/09/12/Functional-Reactive-Programming-in-F/index.html +++ b/2024/09/12/Functional-Reactive-Programming-in-F/index.html @@ -147,6 +147,12 @@ </span> <span class="post-tag"> + <a href="/tags/Archive/"> + Archive + </a> + </span> + + <span class="post-tag"> <a href="/tags/F/"> F# </a> @@ -172,7 +178,10 @@ </div> </div> <div class="post-content"> - <p>Events are everywhere. Almost every program has to handle events, whether it be button clicks in the user interface, listening to sockets in a server, or even a system shutdown notification.</p> + <blockquote> +<p><a target="_blank" rel="noopener" href="https://fsharpforfunandprofit.com/posts/concurrency-reactive/">https://fsharpforfunandprofit.com/posts/concurrency-reactive/</a></p> +</blockquote> +<p>Events are everywhere. Almost every program has to handle events, whether it be button clicks in the user interface, listening to sockets in a server, or even a system shutdown notification.</p> <p>And events are the basis of one of the most common OO design patterns: the “Observer” pattern.</p> <p>But as we know, event handling, like concurrency in general, can be tricky to implement. Simple event logic is straightforward, but what about logic like “do something if two events happen in a row but do something different if only one event happens” or “do something if two events happen at roughly the same time”. And how easy is it to combine these requirements in other, more complex ways?</p> <p>Even if you can successfully implement these requirements, the code tends to be spaghetti like and hard to understand, even with the best intentions.</p> @@ -297,6 +306,11 @@ <nav class="post-nav"> <div class="prev-item"> + <div class="icon arrow-left"></div> + <div class="post-link"> + <a href="/2024/09/15/Advanced-C-binding-using-ocaml-ctypes-and-dune/">Prev</a> + </div> + </div> <div class="next-item"> |