structured-concurrency
Here are 11 public repositories matching this topic...
-
Updated
Apr 7, 2019 - Swift
Some feedback on my first use of libdill, so these are all newbie issues
It is not well explained how to use the int[2] channel you get from chmake
The examples don't help much and sometimes are even wrong like on chdone:
int ch[2];
chmake(ch);
chsend(ch, "ABC", 3, -1); // should be ch[ 1]
chdone(ch); // likely also ch
-
Updated
Jun 2, 2020 - Swift
-
Updated
Jun 4, 2020 - JavaScript
As per #98, in #102 we added proper testing of (almost) all examples in the docs (more land in #99 too).
One of the issues is that some of these examples are also re-implemented in the test suite.
The duplication between examples in examples/ and what's in the tests is hard to avoid currently since the test currently take some of the documented examples and parameterize them with things li
-
Updated
Apr 30, 2020 - Rust
-
Updated
May 26, 2020 - Haskell
-
Updated
Jun 3, 2020 - Assembly
-
Updated
Mar 19, 2020 - Kotlin
-
Updated
Nov 29, 2019 - Python
Improve this page
Add a description, image, and links to the structured-concurrency topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the structured-concurrency topic, visit your repo's landing page and select "manage topics."
Currently in our docs for
open_signal_receiver, we have an example of catching SIGHUP and using it to reload the application configuration. While talking to @wgwz today re: python-trio/snekomatic#41, I discovered that this example is maybe not so great, because readers who aren't already steeped in Unix tr