Andrey Semashev

The message `INFO_MSG` in the .mc file does not have a template string. Also, `AUTO_SCORE_SEVERITY_INFO` has the same value as `AUTO_SCORE_SEVERITY_DEBUG`. You're filling `type_mapping` incorrectly. The mapping is supposed to...

> I did not fully understand your comment about `type_mapping`; could you please give me an example of a change that I can make? `type_mapping` is supposed to convert an...

Any updates? Is this still relevant?

I didn't perform any compilation time comparisons between Boost.MPL and Boost.MP11, but I've seen reports that the latter performs better. I didn't see any numbers, though. I did think about...

I should also note that Boost.Log filter and formatting expressions are based on Boost.Phoenix, which relies on Boost.Fusion, which, in turn, uses Boost.MPL for metaprogramming. So even if Boost.Log itself...

> My understanding is that the counter and date-time part are unrelated, the counter increases whenever a new file is being created. Is my understanding correct? Yes, mostly. The file...

No specific plans. The counter and timestamp are designed to work independently at present and there is no easy way to change it. There is no analysis of a would-be...

You can always [write a custom sink backend](https://www.boost.org/doc/libs/1_77_0/libs/log/doc/html/log/extension.html#log.extension.sinks) that implements the behavior you require. Although that will involve more than just filename generation.

I believe, this is caused by a Boost.Filesystem limitation. The last write timestamps of a file provided by Boost.Filesystem only have granularity of one second, so often all rotated files...

At this point I can't remember where these violations were, I just remember compilers throwing warnings about strict aliasing violations in code other than Boost.Log. Maybe these were fixed by...