Explore >> Select a destination
|
You are here 
|
www.foonathan.net | ||
| | | | |
nrk.neocities.org
|
|
| | | | | ||
| | | | |
brevzin.github.io
|
|
| | | | | Several years ago, I wrote a post about the complexities of implementing comparison operators for optional: Getting in trouble with mixed comparisons. That post was all about how, even just for ==, making a few seemingly straightforward decisions leads to an ambiguity that different libraries handle differently. | |
| | | | |
mpark.github.io
|
|
| | | | | Can we work around the limitations of non-type template parameters? | |
| | | | |
blog.nelhage.com
|
|
| | | If you're familiar with nearly any mainstream programming language, and I asked you to draw a diagram of an array, the array indices, and the array elements, odds are good you'd produce a diagram something like this: In this post, I want to persuade you to replace that image, or, at least, to augment it with an alternate view on the world. I want to argue that, rather than numbering elements of an array, it makes just as much sense, and in many cases more, to number the spaces between elements: | ||
