/explore
|
You are here 
|
mklimenko.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.cppstories.com
|
|
| | | | | For C++17 everyone wanted to have concepts, and as you know, we didn't get them. But does it mean C++17 doesn't improve templates/template meta-programming? Far from that! In my opinion, we get excellent features. Read more for details. Intro Do you work a lot with templates and meta-programming? With C++17 we get a few nice improvements: some are quite small, but also there are notable features as well! | |
| | | | |
mpark.github.io
|
|
| | | | | Can we work around the limitations of non-type template parameters? | |
| | | | |
alvinalexander.com
|
|
| | | [AI summary] An example Java program using JDBC to connect to a Postgres database, execute a SQL query, and print results | ||
