Forthcoming Boost.Charconv review January 15th - 25th, 2024

From: Christopher Kormanyos (e_float_at_[hidden])
Date: 2023-12-23 13:23:26

Dear all,
The review of Boost.Charconv by Matt Borland is scheduledfrom Monday, January 15th to January 25th, 2024.

-----------------------------------------------------
About the library:

Boost.Charconv provides a highly portable and efficient,
C++11 implementation of <charconv>. The API containsfunctions compatible with <charconv>.

Boost.Charconv can be highly useful for portability
and efficiency.

The standard library's <charconv> requires C++17 or higher.
Currently only quite modern compilers such as GCC 11+
and MSVC 19.24+ support both integer and floating-point
conversions in their implementation of <charconv>.

If you are using either of those compilers, Boost.Charconv
is at least as performant as <charconv>, and can be up to
several times faster.

If you are using an older compiler or a language standard
lower than C++17, then there is no <charconv> available.
In such cases, Boost.Charconv provides a highly-viable,
portable and efficient header-only implementation.

Boost.Charconv is a compiled library and does require
a few other Boost libraries to run. The docs providedirections for how to consume with b2, vcpkg and Conanto facilitate this.
Boost.Charconv fits into Boost stylistically and through itshigh quality, its Boost-like testing and its documentation.
Boost.Charconv has been well-received and endorsed
on the Boost-lists and is already being used for prototyping
in several existing Boost libraries. Tool vendors have
expressed interest in Boost.Charconv particularly due
to its high performance and clarity of implementation
details.

docs: https://develop.charconv.cpp.al
git: https://github.com/cppalliance/charconv

---------------------------------------------------

Naturally, you need not wait until the review formally
opens to start reviewing the Charconv library.
Please always state in your review whether you
think the library should be accepted as a Boost library!

Please consider giving feedback on the following general
topics:

- What is your evaluation of the design?
- What is your evaluation of the implementation?
- What is your evaluation of the documentation?
- What is your evaluation of the potential usefulness of the library?
- Did you try to use the library? With what compiler? Did you have any
problems?
- How much effort did you put into your evaluation? A glance? A quick
reading? In-depth study?
- Are you knowledgeable about the problem domain?
Christopher Kormanyos
Boost.Charconv Review Manager
------------------------------