Our great sponsors
-
tlaplus
TLC is a model checker for specifications written in TLA+. The TLA+Toolbox is an IDE for TLA+.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
frunk
Funktional generic type-level programming in Rust: HList, Coproduct, Generic, LabelledGeneric, Validated, Monoid and friends.
So a while back I got interested in how rust could provide parallel/concurrent APIs that prevent deadlocking shared state. I now created a Proof-of-Concept stream processing library that attempts to do that. The library makes prodigious use of heterogeneous lists from the frunk library. The basic idea is that you can build a graph by combining source streams as source nodes and mutexes for state, then you can add nodes which subscribe to subsets of the previous nodes using various combinators. You can either
I think that the traits in this library could be amenable to a proof of lock free behaviour at least for graphs composed entirely of Uniform flow nodes. but right now it's just a hunch. I a little while thinking about it over the last couple of weeks, but a proof, if forthcoming, will definitely be more complicated than I originally hoped. So to the second point of the post title/question does this really disallow deadlocks? I don't know. I think I'll definitely need some kind of proof assistant, and write now am thinking about TLA+, because of it's ability to reason about concurrent systems.
So a while back I got interested in how rust could provide parallel/concurrent APIs that prevent deadlocking shared state. I now created a Proof-of-Concept stream processing library that attempts to do that. The library makes prodigious use of heterogeneous lists from the frunk library. The basic idea is that you can build a graph by combining source streams as source nodes and mutexes for state, then you can add nodes which subscribe to subsets of the previous nodes using various combinators. You can either
Related posts
- Apply generic function to every tuple element
- Self Referencing structs with different generic types
- Is there a convenient way to convert a struct<T> (where all fields are of type T) into struct<U> where U: From<T>?
- constduck: compile-time duck typing and reflection powered by const generics
- Generic associated types encode higher-order functions on types