A C++ library to yeet stuff into the ether
- C++ 95.4%
- Meson 4.6%
|
Jari Ronkainen
646140d31b
Move socket trait types into their own namespace
- Allows using e.g. `yeet::unix_stream_socket`` as an alias to `yeet::base_socket<yeet::traits::unix_stream_socket>` Signed-off-by: Jari Ronkainen <jari.ronkainen@sleepers.garden> |
||
|---|---|---|
| examples | Move socket trait types into their own namespace | |
| include/yeet | Move socket trait types into their own namespace | |
| src | Move socket trait types into their own namespace | |
| subprojects | Add cppxtnd as subproject for IP address types | |
| tests | Initial commit | |
| meson.build | Add cppxtnd as subproject for IP address types | |
| meson.options | Support for listening sockets and std::expected | |
| README.md | Initial commit | |
Yeet
Because sometimes all you want is just sockets wrapped in a nice API
What it does?
Wraps sockets, UART, Bluetooth, and other such I/O channels in an unified, cross-platform manner.
Or at least that's the goal, how far it has gotten is yet to be determined.
What it doesn't do?
Any sort of I/O multiplexing or anything that requires an event loop. That should be done by an actual I/O library or whatever.
libyeet channels should be usable with other such libraries, and pull requests adding required parts to support such libraries are welcome.
Why yeet?
Because the library helps you yeet data to the ether and do it without too much regard to how it's done under the hood.