actix-net
delimited
| actix-net | delimited | |
|---|---|---|
| 3 | 2 | |
| 680 | 2 | |
| 0.4% | - | |
| 8.5 | 10.0 | |
| 2 days ago | about 8 years ago | |
| Rust | C++ | |
| Apache License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
actix-net
-
Monoio – A thread-per-core Rust async runtime with io_uring
> Have any other Rust async runtimes use io_uring/gotten at all good yet?
yes, check out `actix-rt`
https://github.com/actix/actix-net
-
Weird architectures weren't supported to begin with
> For example, this method violates memory safety by handing out multiple mutable references to the same data, which can lead to e.g. a use-after-free vulnerability. I have reported the issue to the maintainers, but they have refused to investigate it. _(issue now deleted)_
-
Having trouble using async libraries
It has been tokio and v1 support is in progress on master branch: https://github.com/actix/actix-net/blob/master/actix-rt/Cargo.toml
delimited
-
Monoio – A thread-per-core Rust async runtime with io_uring
Oh, I have written my own share of userspace C context switching libraries, I know all the gory the details :). For example see my minimalist [1] stackful coroutine library: the full context switching logic is three inline asm instructions (99% of the complexity in that code is to transparently support throwing exceptions across coroutine boundaries with no overhead in the happy path).
You need compiler help for the custom calling convention support and possibly to optimize away the context switching overhead for stackful coroutines, which is something that compilers can already do for stackless coroutines.
The duff device is just a way to simulate stackless coroutines (i.e. async/await or whateverer) in plain C, in a way that the compiler can still optimize quite well.
[1] https://github.com/gpderetta/delimited/blob/master/delimited...
-
Declarative, non-intrusive, compile-time C++ reflection for audio plug-ins
Using gcc extended asm you can pass literal constants to the asm and they will be expanded textually (or at least their address will). I don't think the details are fully documented anywhere and I had to use intel syntax to make it work, but it might be possible even wit AT&T syntax.
Take a look a this[1] for example. See how trampoline, the destructor and the size are passed in with the 'i' constraint and are referred to their value with the %cX constraint (yes, the code is write only and even with a lot of comments I have only the most vague idea of what I was trying to do here).
Probably more work is require for PIC though.
[1] https://github.com/gpderetta/delimited/blob/7e755d643ee45897...
What are some alternatives?
ntex - framework for composable networking services
wg-async - Working group dedicated to improving the foundations of Async I/O in Rust
te - A parser, runtime and specification for the text expression language to make text processing human readable
monoio - Rust async runtime based on io-uring.
crater - Run experiments across parts of the Rust ecosystem!
vst3_public_sdk - VST 3 Implementation Helper Classes And Examples
cortex-m-rt - Minimal startup / runtime for Cortex-M microcontrollers
Fundamental
actix-web-postmortem - Actix project postmortem
essentia - C++ library for audio and music analysis, description and synthesis, including Python bindings
te - C++17 Run-time polymorphism (type erasure) library
DPF - DISTRHO Plugin Framework