libxev
zigcoro
libxev | zigcoro | |
---|---|---|
7 | 1 | |
1,684 | 83 | |
- | - | |
7.9 | 8.5 | |
7 days ago | about 2 months ago | |
Zig | Zig | |
MIT License | BSD Zero Clause License |
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.
libxev
-
Leveraging Zig's Allocators
It scales to complex examples as well. Retained memory would be handled with its own allocator: for a large data structure like an LRU cache, one would initialize it with a pointer to the allocator, and use that internally to manage the memory.
Blocking (or rather, non-blocking, which is clearly what you meant) IO is a different story. Zig had an async system, but it had problems and got removed a couple point releases ago. There's libxev[0] for evented programs, from Mitchell Hashimoto. It's not mature yet but it offers a good solution to single-threaded concurrency and non-blocking IO.
I don't think Zig is the best choice for multithreaded programs, however, unless they're carefully engineered to share little to no memory (using message passing, for instance). You'd have to take care of locking and atomic ops manually, and unlike memory bugs, Zig doesn't have a lot of built-in support for catching problems with that.
A language with manual memory allocation isn't going to be the language of choice for writing web servers, for pretty obvious reasons. But for an application like squeezing the best performance out of a resource-constrained environment, the tradeoffs start to make sense.
[0]: https://github.com/mitchellh/libxev
-
libxev: A cross-platform, high-performance event loop
io_uring support is obviously great & excellent, fulfills the "high performance" part well.
i was not expecting "Wasm + WASI" support at all. that's very cool. implementation is wasi_poll.zig (https://github.com/mitchellh/libxev/blob/main/src/backend/wa...). not to be unkind, but this makes me wonder very much if WASI is already missing the mark, if polling is the solution offered.
gotta say, this is some very understandable clean code. further enhancing my sense that i really ought be playing with zig.
- Show HN: Async tasks in 350 lines of C
-
Epoll: The API that powers the modern internet (2022)
You might be interested in a pure Zig implementation of these primitives by Mitchell in his libxev library: https://github.com/mitchellh/libxev
-
Zig: The Modern Alternative to C
https://github.com/mitchellh/libxev
- one from the Tigerbeetle DB
- Libxev: A cross-platform, high-performance event loop
zigcoro
What are some alternatives?
unzig - Zig with Unused Variables
cr_task.h - Header-only library for asynchronous tasks in C
async_io_uring - An event loop in Zig using io_uring and coroutines
craftos2-lua - Lua fork for CraftOS-PC 2
sokol-tools - Command line tools for use with sokol headers
zig-pico - Not so scuffed Zig project for using the Raspberry Pi Pico SDK
http.zig - An HTTP/1.1 server for zig
mach - zig game engine & graphics toolkit
aviary.sh - Minimal distributed configuration management in bash
bash2048 - Bash implementation of 2048 game
bashttpd - A web server written in bash
bitcoin-bash-tools - Set of bitcoin-related bash functions