(continuing from#331 (comment))

Gotcha, so the last 5 values are unchanged random values that are ignored by the algorithm.

There's another convention that uses- to stand in for such values, e.g.

I think it's a little easier to parse with the non-numeric characters, since it's immediately clear that theycan't be involved in the calculation. If you agree, let's change this to

* `{ ...3], [4,2,1,1], [1,1,1,1], [2,3,3,-], [-,-,-,-] }`.* `{ ..., [-1,2,1,0], [0,0,0,-1], [-1,0,3,-], [-,-,-,-] }`.

Gotcha, so the last 5 values are unchanged random values that are ignored by the algorithm.

These values aren't ignored by the algorithm:

As the documentation states, the input value is copied without modifications if the neighbour value is out of bounds.

Ifinput andoutput parameters point to different memory locations, these values will be copied without modification. I'm afraid that non-numeric characters would mean that the output values are unchanged at all, for example:

input { 1, 2, 3 };output { 4, 5, 6 };valid_items = 0;adjacent_difference(input, output, valid_items);// output should be { 1, 2, 3 } and not { 4, 5, 6 }

The same withstd::adjacent_differencedocumentation. The output for:

std::vector v {2, 4, 6, 8, 10, 12, 14, 16, 18, 20};

is

2 2 2 2 2 2 2 2 2 2

rather than:

- 2 2 2 2 2 2 2 2 2

Do you think it'll be clear from the- notation that the values are copied?

That's a good point -- I'm fine leaving this as-is.

s/on/of/

(this is repeated in a few other docstrings)

There are quite a few places with this typo:

rg "threads on type" | wc -l33

I'll fix this in theblock_scan,block_discontinuity andblock_reduce documentation as well.