static_math
is a C++ library dedicated to compile time mathematics.
static_math
heavily relies on C++ features from the latest standard (C++14) and
even on some planned features that from the Technical Specifications. Therefore, do
not have high expectations, only a few compilers will be able to compile it.
static_math
makes a heavy use of the C++11 keyword constexpr
to reimplement
a number of existing mathematical functions and some new ones. It also provides
a range of classes (rational
, complex
, etc...) whose functions can be used
at compile time too. The library also contains some common mathematical constants.
static_math
has only been made to be usable at compile time and shall not be
used at runtime. It's still possible to use it at runtime though, but it's not
well advised.
Since the library is only meant to be used at compile time, some design choices have been made to improve usability, convenience or safety over performance. For example, the rational numbers are simplified after each operation, which could badly alter the performance in a runtime context.
In order to force the users to think of this library as only a compile-time only
library, some class functions that could have been implemented (without being
compile-time functions) have simply not been implemented. For example, even though
the classes provide arithmetic operators, none of them provides the corresponding
coumpound assignement operators. Another notable design choice is the classes
exposing const
public member variables.
One of static_math
's aims is to be easy to use. The functions are implemented
so that they can be used in a straightforward way. This implies that the user will
not have to deal with complex metaprogramming tricks - even though some are used in
the implementation.
This intuitive feel is the one reason why static_math
needs a recent compiler
since the library will need a heavy support for constexpr
, std::initializer_list
and variadic templates in order to work fine.
Some classes (e.g. rational
and complex
) use public member variables instead
of getters. This simplifies the access to the internals and also ensures that they
cannot be modified after construction.
Some classes such as rational
or complex
make a heavy use of some type traits
facilities such as std::common_type
in order to offer some flexibility. Many
functions accept different number types and return and instance of the common type
of the arguments::
// Two different types used to represent numbers
int a = 5;
long int b = 100000;
// The bigger of them is used as the output type
auto c = gcd(a, b); // type is long int
You can find some documentation in the associated wiki. You can also generate some anemic documentation thanks to the Doxygen comments in the code. If you want to know more about the details, reading the source code might also be an interesting solution: the code should be pretty straightforward and readable enough. Never hesiste to open a documentation issue if you ever feel that some parts of the documentation are not complete enough.