On the STL side the largest headers format uses are string and locale. It may be possible to reduce the amount of code pulled in, but ultimately any TU that needs to format glm vectors probably wants to use them as well. glm may _also_ pull in quite a lot of code. That _does_ pull in quite a bit of code, but the specialization itself shouldn’t be much worse than just using format by itself. (sorry about the code formatting, the blog platform eats templates!)ĭoes just writing that custom formatter slow down compile times more than pulling in format and glm and then formatting with std::format directly (as in the formatter’s format method). Try out format in your own code, and file any bugs on our out GitHub issue tracker.

The behavior of some format specifiers is slightly different (for example the default alignment for void*, and allowing sign specifiers for unsigned types).

There is no support for automatically formatting types with an std::ostream& operator<<(std::ostream&, const T&) overload.

Format strings are not checked at compile time.

None of the miscellaneous formatting functions like fmt::print or fmt::printf are supported.

The standardized library is based on the existing, a quick list of differences from the standardized version of the library: C++20 adds a new text formatting facility to the standard library, designed primarily to replace snprintf and friends with a fast and type safe interface.

Visual studio format