microfmt
Zero-allocation C++ formatting for constrained environments
Loading...
Searching...
No Matches
Namespaces
reloco.hpp File Reference

Single re-export of every `reloco` type and annotation microfmt builds on. More...

#include <reloco/array.hpp>
#include <reloco/checked_value.hpp>
#include <reloco/duration.hpp>
#include <reloco/expected.hpp>
#include <reloco/instant.hpp>
#include <reloco/lifetime.hpp>
#include <reloco/rvalue_safety.hpp>
#include <reloco/span.hpp>
#include <reloco/string_view.hpp>
#include <reloco/value_ptr.hpp>
#include <reloco/value_ref.hpp>
Include dependency graph for reloco.hpp:
This graph shows which files directly or indirectly include this file:

Go to the source code of this file.

Namespaces

namespace  microfmt
 
namespace  microfmt::unsafe
 

Detailed Description

Single re-export of every `reloco` type and annotation microfmt builds on.

reloco (https://github.com/jplcz/reloco) owns lifetime-safety annotations and hardened, checked container/wrapper types; microfmt injects them into the microfmt namespace so existing microfmt::X call sites keep working unchanged. Macro annotations (e.g. RELOCO_LIFETIMEBOUND, RELOCO_BLOCK_RVALUE_ACCESS) are used directly, with no MICROFMT_* alias, since macros have no namespacing. See Lifetime safety and Hardened containers for the underlying conventions.