Patrik Jonsson

The index type is size_t. As long as you compile as 64-bit, the max size of the array should not be a limitation. On Tue, Apr 9, 2019, 18:13 Guanghao...

I have concerns about such a change, because I suspect that returning references will inhibit automatic vectorization on the platforms that support this. If you're operating on strings, your operations...

All I know is that when I coded up the vectorization improvements a long time ago, there were numerous things that "should" not matter that did. The blitz ETs tax...

The trouble with intrinsics is that they're tied to the architecture, so it seems messy to get something that works in general. Although, looking at https://gcc.gnu.org/onlinedocs/gcc/Vector-Extensions.html, they may be generic...

I agree that with C++11 much ugliness could be removed. Just being able to use "auto" for types would probably cut the code in half... ;-) Two points, however: 1....

TinyVector supports templated, vectorized expressions. Its performance is crucial for heavy use of fixed-size vectors (e.g. 3-d vectors etc). std::array does not support any of that. While this behavior for...

Sorry for the slow response, I was traveling. TinyVector is used for the internal offset and bounds calculations in blitz, and for the blocked Array expressions used to facilitate SIMD...

This is true, but it has no math operators, let alone ones using something similar to the blitz ET machinery. On Sun, Apr 7, 2019, 09:59 Elizabeth Fischer wrote: >...

Unless I'm mistaken, std::array does not define any math operators. That said, it might be possible to usefully leverage it as the backend to TinyVector.

Hi all, I was hoping to use TinyG with multiple tools, but the lack of length compensation seems to be a killer for this. I can see how the tool...