Add an optional final qualifier to types

When building with GCC's -Wfinal-types, a lot of types of spdlog
are marked as being more optimizable if they were marked final.

This patch adds a possibility for the user of the library to `#define SPDLOG_FINAL final`
and enjoy potentially better performance : GCC is then able to replace virtual calls by true
function calls if it can ensure that there are no derived types).

By default SPDLOG_FINAL is defined to nothing to not break existing code that
may be inheriting of some of these types for some reason.

Android_logger conditionally apply its own formatting

Android_logger apply its own formatting to every print by adding timestamps, severity, thread and process ids, thus the option flag in the ctor

Fix typo immediatly immediately

fix typos in base_sink.h

fix typo potentialy to potentially

Fix typo in comment Unkown to Unknown

Fix typo Unkown to Unknown

Update example in README.md

[#404] Reading past valid address with multisink logger

- Initialising atomic value

See examples at http://stackoverflow.com/q/36320008/706456
This issue was discovered with dr memory tool on Windows platform, Visual Studio 2015 C++ 11

- Initialising atomic value

See examples at http://stackoverflow.com/q/36320008/706456
This issue was discovered with dr memory tool on Windows platform, Visual Studio 2015 C++ 11

Disambiguate fmt logging methods that are using variadic templates.

As variadic template arguments can be zero length, we need to specify that at least one fmt argument is provided, to distinguish these methods from the existing trivial method that takes no fmt arguments.

Without this, static analysers such as ReSharper flag the logging calls as errors.

Update README.md

fmt: update bundled fmt to 3.0.1 (7fa8f8f)

Signed-off-by: Damien Zammit <damien@zamaudio.com>

Use double-braces in std::array initialization.

Don't hardcode '.txt.' log file name suffix (resolve #333)

Signed-off-by: Ľubomír Carik <Lubomir.Carik@gmail.com>