scnlib

#include <scn/scan.h>
#include <print> // for std::println (C++23)

int main() {
    // Read two integers from stdin
    // with an accompanying message
    if (auto result =
            scn::prompt<int, int>("What are your two favorite numbers? ", "{} {}")) {
        auto [a, b] = result->values();
        std::println("Oh, cool, {} and {}!", a, b);
    } else {
        std::println(stderr, "Error: {}", result.error().msg());
    }
}

Try out in Compiler Explorer.

What is this?

scnlib is a modern C++ library for replacing scanf and std::istream. This library attempts to move us ever so much closer to replacing iostreams and C stdio altogether. It's faster than iostream (see Benchmarks), and type-safe, unlike scanf. Think {fmt} or C++20 std::format, but in the other direction.

This library is the reference implementation of the ISO C++ standards proposal P1729 "Text Parsing".

Documentation

The documentation can be found online, at https://scnlib.dev.

To build the docs yourself, build the scn_docs target generated by CMake. These targets are generated only if the variable SCN_DOCS is set in CMake (done automatically if scnlib is the root project). The scn_docs target requires Doxygen, Python 3.8 or better, and the pip3 package poxy.

Examples

See more examples in the examples/ folder.

Reading a std::string

#include <scn/scan.h>
#include <print>

int main() {
    // Reading a std::string will read until the first whitespace character
    if (auto result = scn::scan<std::string>("Hello world!", "{}")) {
        // Will output "Hello":
        // Access the read value with result->value()
        std::println("{}", result->value());
        
        // Will output " world":
        // result->range() returns a subrange containing the unused input
        // C++23 is required for the std::string_view range constructor used below
        std::println("{}", std::string_view{result->range()});
    } else {
        std::println("Couldn't parse a word: {}", result.error().msg());
    }
}

Reading multiple values

#include <scn/scan.h>

int main() {
    auto input = std::string{"123 456 foo"};
    
    auto result = scn::scan<int, int>(input, "{} {}");
    // result == true
    // result->range(): " foo"
    
    // All read values can be accessed through a tuple with result->values()
    auto [a, b] = result->values();
    
    // Read from the remaining input
    // Could also use scn::ranges::subrange{result->begin(), result->end()} as input
    auto result2 = scn::scan<std::string>(result->range(), "{}");
    // result2 == true
    // result2->range().empty() == true
    // result2->value() == "foo"
}

Reading from a fancier range

#include <scn/scan.h>

#include <ranges>

int main() {
    auto result = scn::scan<int>("123" | std::views::reverse, "{}");
    // result == true
    // result->begin() is an iterator into a reverse_view
    // result->range() is empty
    // result->value() == 321
}

Repeated reading

#include <scn/scan.h>
#include <vector>

int main() {
    std::vector<int> vec{};
    auto input = scn::ranges::subrange{"123 456 789"sv};
    
    while (auto result = scn::scan<int>(input), "{}")) {
        vec.push_back(result->value());
        input = result->range();
    }
}

Features

• Blazing fast parsing of values (see Benchmarks)
• Modern C++ interface, featuring
  • type safety (variadic templates, types not determined by the format string)
  • convenience (ranges)
  • ergonomics (values returned from scn::scan, no output parameters)
• "{python}"-like format string syntax
  • Including compile-time format string checking
• Minimal code size increase (in user code, see Benchmarks)
• Usable without exceptions, RTTI, or <iostream>s
  • Configurable through build flags
  • Limited functionality if enabled
• Supports, and requires Unicode (input is UTF-8, UTF-16, or UTF-32)
• Highly portable
  • Tested on multiple platforms, see CI
  • Works on multiple architectures, tested on x86, x86-64, arm, aarch64, riscv64, ppc64le, and riscv64

Installing

scnlib uses CMake. If your project already uses CMake, integration should be trivial, through whatever means you like: make install + find_package, FetchContent, git submodule + add_subdirectory, or something else.

There are community-maintained packages available on Conan and on vcpkg.

The scnlib CMake target is scn::scn

# Target with which you'd like to use scnlib
add_executable(my_program ...)
target_link_libraries(my_program scn::scn)

See docs for usage without CMake.

Compiler support

A C++17-compatible compiler is required. The following compilers are tested in CI:

• GCC 7 and newer
• Clang 8 and newer
• Visual Studio 2019 and 2022

Including the following environments:

• 32-bit and 64-bit builds on Windows
• libc++ on Linux
• gcc on Alpine Linux
• AppleClang and gcc on macOS 12 (Monterey) and 14 (Sonoma)
• clang-cl with VS 2019 and 2022
• MinGW and MSys2
• GCC on armv6, armv7, aarch64, riscv64, s390x, and ppc64le
• Visual Studio 2022, cross-compiling to arm64

Benchmarks

Run-time performance

All times below are in nanoseconds of CPU time. Lower is better.

Integer parsing (int)

Floating-point number parsing (double)

String "word" (whitespace-separated character sequence) parsing (string and string_view)

Conclusions

• scn::scan is always faster than using stringstreams and sscanf
• std::from_chars/fast_float::from_chars is faster than scn::scan, but it supports fewer features
• strtod is slower than scn::scan, and supports fewer features
• scn::scan_value is slightly faster compared to scn::scan
• scn::scan_int is faster than both scn::scan and scn::scan_value
• strtol is ~on-par with scn::scan_int.
• scn::scan_int_exhaustive_valid is blazing-fast.

About

Above,

• "Test 1" refers to scanning a single value from a string, which only contains the text representation for that value. The time used for creating any state needed for the scanner is included, for example, constructing a stringstream. This test is called "single" in the benchmark sources.
• "Test 2" refers to the average time of scanning a value, which contains multiple values in their text representations, separated by spaces. The time used for creating any state needed for the scanner is not included. This test is called "repeated" in the benchmark sources.
• The string test is an exception: strings are read one after another from a sample of Lorem Ipsum.

The difference between "Test 1" and "Test 2" is most pronounced when using a stringstream, which is relatively expensive to construct, and seems to be adding around ~50ns of runtime. With sscanf, it seems like using the %n specifier and skipping whitespace are really expensive (~400ns of runtime). With scn::scan and std::from_chars, there's really no state to construct, and the results for "Test 1" and "Test 2" are thus quite similar.

These benchmarks were run on a Fedora 40 machine, running the Linux kernel version 6.8.9, with an AMD Ryzen 7 5700X processor, and compiled with clang version 18.1.1, with -O3 -DNDEBUG -march=haswell and LTO enabled. These benchmarks were run on 2024-05-23 (commit 3fd830de).

The source code for these benchmarks can be found in the benchmark directory. You can run these benchmarks yourself by enabling the CMake variable SCN_BENCHMARKS. This variable is ON by default, if scnlib is the root CMake project, and OFF otherwise.

$ cd build
$ cmake -DSCN_BENCHMARKS=ON \
        -DCMAKE_BUILD_TYPE=Release -DCMAKE_INTERPROCEDURAL_OPTIMIZATION=ON \
        -DSCN_USE_HASWELL_ARCH=ON ..
$ cmake --build .
# choose benchmarks to run in ./benchmark/runtime/*/*_bench
$ ./benchmark/runtime/integer/scn_int_bench

Executable size

All sizes below are in kibibytes (KiB), measuring the compiled executable. "Stripped size" shows the size of the executable after running strip. Lower is better.

Release build (-O3 -DNDEBUG + LTO)

Size of scnlib shared library (.so): 1.7M

Minimized (MinSizeRel) build (-Os -DNDEBUG + LTO)

Size of scnlib shared library (.so): 1.1M

Debug build (-g -O0)

Size of scnlib shared library (.so): 20M

Conclusions

When using optimized builds, depending on compiler flags, scnlib provides a binary, the size of which is within ~5% of what would be produced with scanf or <iostream>s. In a Debug-environment, scnlib is ~5x bigger when compared to scanf or <iostream>. After stripping the binaries, these differences largely go away, except in Debug builds.

About

In these tests, 25 translation units are generated, in all of which values are read from stdin five times. This is done to simulate a small project. scnlib is linked dynamically, to level the playing field with the standard library, which is also dynamically linked.

The code was compiled on Fedora 40, with GCC 14.1.1. See the directory benchmark/binarysize for the source code.

You can run these benchmarks yourself by enabling the CMake variable SCN_BENCHMARKS_BINARYSIZE. This variable is ON by default, if scnlib is the root CMake project, and OFF otherwise.

$ cd build
# For Debug
$ cmake -DCMAKE_BUILD_TYPE=Debug \
        -DSCN_BENCHMARKS_BINARYSIZE=ON \
        -DBUILD_SHARED_LIBS=ON ..
# For Release and MinSizeRel,
# add -DCMAKE_BUILD_TYPE=$BUILD_TYPE and
# -DCMAKE_INTERPROCEDURAL_OPTIMIZATION=ON

$ cmake --build .
$ ./benchmark/binarysize/run_binarysize_bench.py ./benchmark/binarysize $BUILD_TYPE

Build time

Build time

Time is in seconds of CPU time (user time + sys/kernel time). Lower is better.

Memory consumption

Memory is in mebibytes (MiB) used while compiling. Lower is better.

Conclusions

Code using scnlib takes around 2x longer to compile compared to <iostream>, and also uses around 1.5x more memory. Release builds seem to be slightly faster as compared to Debug builds.

About

These tests measure the time it takes to compile a binary when using different libraries. The time taken to compile the library itself is not taken into account (the standard library is precompiled, anyway).

These tests were run on a Fedora 40 machine, with an AMD Ryzen 7 5700X processor, using GCC version 14.1.1. The compiler flags used for a Debug build were -g, and -O3 -DNDEBUG for a Release build.

You can run these benchmarks yourself by enabling the CMake variable SCN_BENCHMARKS_BUILDTIME. This variable is ON by default, if scnlib is the root CMake project, and OFF otherwise. For these tests to work, c++ must point to a GCC-compatible C++ compiler binary, and a somewhat POSIX-compatible /usr/bin/time must be available.

$ cd build
$ cmake -DSCN_BENCMARKS_BUILDTIME=ON ..
$ cmake --build .
$ ./benchmark/buildtime/run-buildtime-tests.sh

Acknowledgements

The contents of this library are heavily influenced by {fmt} and its derivative works.
https://github.com/fmtlib/fmt

The design of this library is also inspired by the Python parse library:
https://github.com/r1chardj0n3s/parse

Third-party libraries

fast_float for floating-point number parsing:
https://github.com/fastfloat/fast_float

NanoRange for a minimal <ranges> implementation:
https://github.com/tcbrindle/NanoRange

License

scnlib is licensed under the Apache License, version 2.0.
Copyright (c) 2017 Elias Kosunen
See LICENSE for further details.