Breno Rodrigues Guimarães
Breno Rodrigues Guimarães
It looks to me that these two are very similar in what they are trying to say: https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#f55-dont-use-va_arg-arguments https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#-es34-dont-define-a-c-style-variadic-function They both talk about lack of type safety: F.55: `Reading from...
The fundamental building blocks of this library can be seen as: ``` template auto allocate_adjacent_arrays(std::integral auto... sizes) -> std::tuple; ``` This function would allocate a single block of memory that...
A lot of the code is templated but it would be nice to have code coverage infrastructure.
The library contains a benchmark directory with a single benchmark. It would be nice to have a check that the performance using the library is actually better than the performance...
So far we have 0 real world users :) It would be nice to use this library in some project and we would link this project here as a user....
I have seen a lots of confused feedback from people who did not understand what the library does and how it helps. It would be nice to have a more...
The library has little to no comments. It would be great to go over all functions and tricky code and document it.
Today the library only creates the Object + arrays in that sequence. It would be nice to have a "BackwardAdjacentArray" which would cause the layout to be: ``` | arrays...
The main test file (tests/unit/basic.test.cpp) contains a lot of duplicated code, it's not very thorough and doesn't test many of the corner cases. It would be nice to cleanup, reuse,...
We have a single benchmark using a graph. New cool applications to showcase the power of the library wanted.