|
You are here |
quuxplusone.github.io | ||
| | | | |
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! | |
| | | | |
www.reedbeta.com
|
|
| | | | | Pixels and polygons and shaders, oh my! | |
| | | | |
mpark.github.io
|
|
| | | | | A visitation mechanism for `std::variant`. | |
| | | | |
blog.martinig.ch
|
|
| | | Architecture is an important asset for good programming and the notion of "pattern" is here to help us apply already trusted code architecture solutions to common problems. Jason McDonald has done a wonderful job to group some of them in a document that should be useful to most software developers. Go to his blog to | ||