Is it worth it?

This is a short section which should help you decide whether to use this library.

So, is this a weekend project or is this something more serious?

Templatious library was born out of hatred for boilerplates. Everything that was written was written so that user would have to type less, make less mistakes and get mostly compile time errors after making a mistake.

Templatious library has a 99.9% line test coverage always enforced by continous integration on variety platforms and compilers. Users are free to and encouraged and blessed for donating tests.

Templatious library prefers compile time errors over runtime errors. Usually, if your code compiles it just works (although, template error messages are sometimes not the friendliest).

Due to templatious nature of this library (pun totally intended) and very explicit nature of templates compiler can optimize high level constructs in templatious to boilerplate performance had you written a boilerplate. Don't take my word for it - compile and run this project.

Templatious library is a HEADER ONLY library, meaning no linkage burden on a user. Add one directory to your includes, include (usually) one header in your source and off you go - all the rich ecosystem of templatious is at your disposal.

STL collections supported by default in templatious library can be extended by custom third party adapter library.

Also, templatious library is thoroughly documented and most of the time with examples.

The solidity of this library is further enforced with the following tools that are run on the test suite:

  • valgrind
  • llvm address sanitizer
  • llvm thread sanitizer
  • llvm undefined behaviour sanitizer

Compilers supported:
g++-4.8 or later
clang++-3.5 or later
mingw-4.9 or later

And last but not least, templatious library is licensed under permissive MIT license.

All ears? Check out the quickstart.