/explore
|
You are here 
|
weberdominik.com | ||
| | | | |
effectivetypescript.com
|
|
| | | | | Effective TypeScript: The Golden Rule of Generics | |
| | | | |
codewithstyle.info
|
|
| | | | | Advanced types section of TypeScript docs mentions some very useful built-in types as examples of conditional types and mapped types. I was surprised | |
| | | | |
yakovfain.com
|
|
| | | | | This blog is a part of my TypeScript series, and the previous ones are: 1. Why program in TypeScript 2. Structural vs nominal typing 3. Getting started with TypeScript classes 4. Access modifiers public, private, and protected 5. Abstract classes 6. enums 7. An intro to TypeScript generics 8. TypeScript mapped types. Part 1 In... | |
| | | | |
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! | ||
