https://github.com/potatoengine/nanofmt

Copyright (c) Sean Middleditch and contributors

nanofmt is released under the MIT license.

nanofmt uses the Dragonbox reference implementation which released under either the Apache License Version 2.0 with LLVM Exceptions or the Boost Software License Version 1.0.

Documentation

char buffer[128];

char const* const end = nanofmt::format_to_n(
        buffer,
        sizeof buffer,
        "Hello, {0}! You are visitor {1}.",
        user_name,
        visitor_count);

// void write_log(char const* str, size_t length);
write_log(buffer, end - buffer);

nanofmt aims to provide a lite-weight semi-compatible implementation of the excellent fmtlib. This can be used in environments or team cultures where neither std::format nor fmtlib are available for use.

The primary motivation for nanofmt is to minimize dependencies on standard C++ headers and to minimize compile time. nanofmt does not aim to offer the fastest runtime efficiency, the most features, fmtlib or std::format compatibility, nor the most portable implementation.

C++17 is required.

Most notably, nanofmt only supports the (v)format_to_n interfaces to basic char* buffers and does not support any other character type or output iterators. There are custom (v)format_to wrappers that work only with the provided buffer type, which itself is just a wrapper around char* buffers.

nanofmt does not aim to be a true drop-in replacement of fmtlib, even for the interfaces found in both libraries. Some interfaces have been modified to appeal more to "C with Classes" programmers; this is not a judgement of modern C++, just an acquiescence to the prevalent tastes and opinions in the industries targetted by nanofmt (primarily the AAA game industry).

Support for floating-point types can optionally be disabled via the NANOFMT_FLOAT CMake option. Pass -DNANOFMT_FLOAT=OFF on the CMake command line to disable.

If you're in doubt, use fmtlib! It is in almost every conceivable way more complete, more runtime efficient, more reliable, better maintained, more portable, and otherwise superior.

Use nanofmt if your organization or team has decided they won't use fmtlib because of its standard library dependencies or its large-ish header sizes.

Use nanofmt if your organization or team believes that snprintf is the superior formatting library, other than limitations created by C varargs.

Literally anytime that you have the option of using std::format or fmtlib, you should prefer using those instead!

If you're not sure if nanofmt is the right fit for your project, then it isn't. :)