Explore >> Select a destination
|
You are here 
|
isocpp.org | ||
| | | | |
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! | |
| | | | |
mpark.github.io
|
|
| | | | | Can we work around the limitations of non-type template parameters? | |
| | | | |
jguegant.github.io
|
|
| | | | | This post is part of a series of posts: Part 1 - Beating std::unordered_map Part 2 - Growth Policies & The Schrodinger std::pair Part 3 - The wonderful world of iterators and allocators (Current) Part 4 - ... (Coming Soon) In the previous post, we prepared our data-structure to be able to store our ... | |
| | | | |
jerf.org
|
|
| | | |||
