/explore
|
You are here 
|
isocpp.org | ||
| | | | |
brevzin.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! |
|
| | | | | ||
| | | | |
0xd34df00d.me
|
|
| | | | | ||
| | | | |
andrewkelley.me
[AI summary] The blog post discusses the challenges and solutions for handling asynchronous I/O in Zig, focusing on cancellation, resource management, and concurrency. It highlights how cancellation is a key primitive for managing resources and avoiding leaks, while concurrency is essential for avoiding deadlocks in producer-consumer scenarios. The post also touches on the importance of using appropriate APIs like `concurrent` instead of `async` when true concurrency is needed, and the ongoing design work for stackless coroutines and I/O interfaces. |
|
| | | |||
