#
structured-concurrency
Here are 13 public repositories matching this topic...
Coroutines, structured concurrency and CSP for Swift on macOS and Linux.
linux
swift
csp
performance
server
coroutines
fibers
travis-badge
server-side-swift
synchronous
codecov-url
swiftpm
swift-url
codebeat-url
non-blocking
codecov-badge
venice
green-threads
codebeat-badge
swift-badge
mit-badge
structured-concurrency
-
Updated
Apr 7, 2019 - Swift
Swift coroutines for iOS, macOS and Linux.
macos
linux
swift
ios
promises
async
asynchronous
atomic
scheduler
coroutines
thread
dispatch
multithreading
await
lock-free
async-await
futures
combine
coroutine
structured-concurrency
-
Updated
Jun 20, 2021 - Swift
Fine-grained concurrency for Ruby
ruby
http
networking
websocket
http2
concurrency
libev
structured-concurrency
polyphony
io-uring
iouring
ruby-fibers
-
Updated
Aug 6, 2021 - C
A framework for Node and the browser that makes building concurrent systems easy to get right.
-
Updated
Aug 6, 2021 - TypeScript
goodboy
commented
Aug 3, 2020
I totally forgot we have machinery for this in the "muti program" tests. We can likely reuse this on the "external ctrl-c" tests as well!
-
Updated
Apr 22, 2021 - Haskell
Primitive for structured concurrency.
-
Updated
Jun 11, 2021 - Rust
Functional programming in terms of dynamical systems. A declarative approach to application design.
kotlin
functional
dsl
declarative
process
dynamical-systems
coroutine
structured-concurrency
process-dsl
-
Updated
Mar 19, 2020 - Kotlin
Simple C Linux application that can be used to detect sequences of edges on GPIO inputs
-
Updated
Jan 27, 2021 - C
A minimalistic wrapper for google api services which implements some common intermediate-level functionality which may be useful for wide range of projects.
-
Updated
Aug 6, 2021 - Swift
On the path to understanding concurrency...
-
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."
What should happen if deliver_cancel raises an exception? In the current implementation, the shielded cancel scope will prevent it from propagating until the process exits, which might take a while if the crash occurred before signaling the process in any way. Maybe on exception from a user-specified deliver_cancel we should call the default deliver_cancel to kill the process? Or just kill() since