FATAL log level..?

[Talkless]

Qt has qFatal that prints and aborts application.

I wonder how spdlog users implement this, do they all create their own helper? Maybe worth having something like that in spdlog? Or ability (or custom handler of sorts?) to configure so that critical will abort?

[tt4g]

In my personal opinion, logging libraries do not need to provide a feature that forces applications to terminate.
Even if a fatal error occurs, some applications must begin the termination process only after releasing resources. For such applications, it is problematic if the application is terminated automatically simply because a fatal error was logged at the FATAL log level.

In addition, spdlog provides asynchronous logging features. If the application crashes immediately after a FATAL log function is called, asynchronous log output is not guaranteed.

[Talkless]

If the application crashes immediately after a FATAL log function is called, asynchronous log output is not guaranteed.

Would spdlog::shutdown(); help before std::abort() ?

[tt4g]

Yes, spdlog::shutdown() flushes the logs as much as possible.