You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the FileLogHandler opens the target file, writes the message and closes the file again for each log message, which is an unnecessary overhead.
Instead, the file should be opened once on construction and closed on destruction of the log handler. If it is desired to ensure that log messages are written to disk in case of a system crash, std::ostream::flush should be used. This behavior could be configurable.
The text was updated successfully, but these errors were encountered:
Currently, the
FileLogHandler
opens the target file, writes the message and closes the file again for each log message, which is an unnecessary overhead.Instead, the file should be opened once on construction and closed on destruction of the log handler. If it is desired to ensure that log messages are written to disk in case of a system crash,
std::ostream::flush
should be used. This behavior could be configurable.The text was updated successfully, but these errors were encountered: