Explore >> Select a destination
|
You are here 
|
0xd34df00d.me | ||
| | | | |
www.think-cell.com
|
|
| | | | | [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. | |
| | | | |
www.foonathan.net
|
|
| | | | | In my previous blog post, weve discussed the static constexpr std::integral_constant idiom to specify the size of a range at compile-time. Unlike the standard, our (think-cells) ranges library at think-cell already supports compile-time sizes natively, so I was eager to try the idiom there and see how it works out in practice. namespace tc { template constexpr auto size(Rng&& rng); // runtime-size of a range, like std::ranges::size template requires tc::has_constexpr_size constexpr auto constexpr_size = ... | |
| | | | |
mpark.github.io
|
|
| | | | | Can we work around the limitations of non-type template parameters? | |
| | | | |
bisco.org
|
|
| | | A couple of weeks ago there was an article on the Freexian blog about Using JavaScript in Debusine without depending on JavaScript. It describes how JavaScript is used in the Debusine Django app, namely "for progressive enhancement rather than core functionality". This is an approach I also follow when implementing web interfaces and I think developments in web technologies and standardization in recent years have made this a lot easier. | ||
