/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 quuxplusone.github.io
Perennial impossibilities of C++ - Arthur O'Dwyer - Stuff mostly about C++
| | www.foonathan.net
Tricks with Default Template Arguments
4.6 parsecs away

Travel
| | Just like regular function parameters, template parameters can also have default parameters. For class templates, this behaves mostly just like default function arguments: if you pass fewer template arguments than required, default template arguments are used to fill the remaining places. However, for function templates, it gets more complicated as template parameters for functions can be deduced by the normal function arguments. This leads to some interesting side-effects. In particular, default argumen...
| | www.think-cell.com
Compile-time sizes for range adaptors | think-cell
5.0 parsecs away

Travel
| | [AI summary] The blog post discusses techniques for implementing compile-time size calculations for range adaptors in C++ using think-cell's library, focusing on forwarding size properties and avoiding code duplication.
| | mklimenko.github.io
Automate your C library type-based overload resolutions with C++17 | GNSS C++ solutions
4.9 parsecs away

Travel
| | Every time I work with a C library, I miss the power and capability of the type system C++ provides. That's why I developed a simple C++17 header-only helper library to pack the multiple type-dependent C-style functions into single overload deduced at compile-time. No external libraries are required. Repo link: https://github.com/MKlimenko/plusifier. Currently, it's just the header and a compile-time test file, CMake integration coming soon.
| | rust-lang.github.io
0236-error-conventions - The Rust RFC Book
21.5 parsecs away

Travel
| [AI summary] A Rust RFC proposes formal conventions for error handling that distinguish between catastrophic errors, contract violations, and obstructions to guide library API design.