1
2
Fork
You've already forked chic
0
📨 Realtime-safe channels in C https://rubiefawn.codeberg.page/chic
  • C 93.6%
  • CMake 3.6%
  • C++ 2.2%
  • Nushell 0.6%
Fawn 6a9e700d47
All checks were successful
Build, test, & publish docs / build (push) Successful in 41s
Build, test, & publish docs / docs (push) Successful in 1m48s
Initial commit
2026年07月13日 13:13:25 -06:00
.forgejo/workflows Initial commit 2026年07月13日 13:13:25 -06:00
docs Initial commit 2026年07月13日 13:13:25 -06:00
include Initial commit 2026年07月13日 13:13:25 -06:00
src Initial commit 2026年07月13日 13:13:25 -06:00
tests Initial commit 2026年07月13日 13:13:25 -06:00
.clangd Initial commit 2026年07月13日 13:13:25 -06:00
.gitignore Initial commit 2026年07月13日 13:13:25 -06:00
CMakeLists.txt Initial commit 2026年07月13日 13:13:25 -06:00
LICENSE.md Initial commit 2026年07月13日 13:13:25 -06:00
README.md Initial commit 2026年07月13日 13:13:25 -06:00
todo.txt Initial commit 2026年07月13日 13:13:25 -06:00

📨 chic

Buffered channels, such as the Go programming language's chan or Plan 9's Channel, written in C17.

These channels are suitable for inter-process communication in realtime applications as they do not use mutex, semaphore, or anything else that blocks or requires a context switch. They synchronize using atomic operations only. They are intended to have better/bounded worst-case performance, even at the expense of average-case performance.

These channels support sending and receiving batches of items, and also provide methods to safely read and write directly to their underlying ringbuffer for zero-copy communication.

Chic provides four flavors of channels:

  • Multiple-producer, multiple-consumer: If you're not sure what you need, use this one. This is most similar to Go's chan.
  • Multiple-producer, single-consumer: Receiving from the channel is optimized under the assumption that only one thread receives from the channel.
  • Single-producer, multiple-consumer: Sending to the channel is optimized under the assumption that only one thread sends to the channel.
  • Single-producer, single-consumer: All channel operations are optimized under the assumption that only one thread sends to the channel and only one thread receives from the channel.

Usage

Chic is a work-in-progress and requires further testing and refinement before usage is advisable. That said, basic examples can be found in tests/*p*c_demo.c.

Building

Chic depends on the CMake build system and the presence of a compiler that supports both C17 and <stdatomic.h>. The optional tests require support for <threads.h>.

Build Chic as a static library (preferred):

cmake -B build && cmake --build build

Build Chic as a dynamic library:

cmake -DBUILD_SHARED_LIBS=ON -B build && cmake --build build

Documentation

Documentation is available at rubiefawn.codeberg.page/chic.

HTML documentation can be built locally if you have Doxygen installed by running:

cmake -B build && cmake --build build --target docs

License

Chic is available under the terms of the Mozilla Public License, v. 2.0.

The intent is to allow anybody to freely use and link Chic to any other software under any other license, as long as Chic itself remains unmodified. If you modify Chic, those derivative works must be released under the MPL-2.0. In other words, use Chic freely for any purpose, but in turn, please freely share any changes you make to it.

Resources

📮 Blog Posts

📺 Videos

📃 Papers

🔖 Miscellaneous