Sane C++ Libraries

600+ GitHub stars Still growing

25 Libraries Cross-platform building blocks

1 Skill Repo skill available now

3 Platforms macOS, Windows, Linux

Dependency map

Library graph

Most libraries have no library-level dependency. A few higher-level libraries build on those small pillars, so you can pick one useful piece without switching your whole project to Sane C++.

The reasons

Why this shape?

Sane C++ Libraries tries to blend the compactness of single-file libraries with the convenience of a small runtime. You can start with one library, a unity-build checkout, or the full SC::Build workflow without turning your project into a framework.

Independent libraries

A small amount of code duplication is accepted in order to keep many libraries isolated.

Working like a runtime

It brings ready-to-use runtime pieces that C++ projects often miss, closer to what developers expect from JavaScript or Python.

Composable by design

Libraries stay useful on their own, but their explicit boundaries make them easy to combine when a project grows.

Contributions

PR means Prompt Request

The maintainer should be able to recreate or adapt the work from a clean checkout. The prompt is evaluated as durable context, not as a demand for byte-identical code.

Title: HttpClient: Add a request timeout option
Objective: fail requests that take too long
Context: fit the existing streaming-first design
Constraints: no hidden allocations, preserve platform backends
Validation: run the focused HttpClient tests in Debug

Open the repository skill

Investment level

Small, medium or big

Start with the simplest model: one generated header for one library.

#include "SaneCppFoundation.h"
#define SANE_CPP_IMPLEMENTATION
#include "SaneCppFoundation.h"

Clone the repo, add SC.cpp to your build, and include the libraries you need.

git clone https://github.com/Pagghiu/SaneCppLibraries.git
# add SC.cpp to your build
# include Libraries/Foundation/*.h

Use SC::Build when you want the full project workflow: examples, tests, native builds, cross targets, and package-managed toolchains.

./SC.sh build configure
./SC.sh build compile SCTest
./SC.sh build run SCExample

Libraries

Not a framework

The project is not a framework. The libraries try to stay as independent as possible, even at the cost of some internal duplication, while still working smoothly together. You can use one or two of them without pulling in the whole codebase.

Full catalog

Foundation Primitive types, asserts, compiler macros, Function, Span, Result

Usable

Async Async I/O (files, sockets, timers, processes, fs events, threads wake-up)

MVP

Plugin Minimal dependency based plugin system with hot-reload

MVP

Http HTTP parser, server and client

Draft

Process Create child processes and chain them (also usable with Async library)

Usable

Reflection Describe C++ types at compile time for serialization