/explore
|
You are here 
|
www.think-cell.com | ||
| | | | |
mpark.github.io
Can we work around the limitations of non-type template parameters? |
|
| | | | | ||
| | | | |
www.foonathan.net
The size of std::array is known at compile-time given the type. Yet it only provides a regular .size() member function: template struct array { constexpr std::size_t size() const { return N; } }; This is annoying if you're writing generic code that expects some sort of compile-time sized range. |
|
| | | | | ||
| | | | |
rodusek.com
Getting the name of a type in C++ is a hassle. For something that should be trivially known by the compiler at compile-time, the closest thing we have to getting the type in a cross-platform way is to use std::type_info::name which is neither at compile-time, nor is it guaranteed to be human-readable. In fact, both GCC and Clang actually return the compiler's mangled name rather than the human-readable name we are used to. Let's try to make something better using the modern utilities from c++17 and a little creative problem solving! |
|
| | | | | ||
| | | | |
mcyoung.xyz
|
|
| | | |||
