Francesco Rizzi

icon company NexGen Analytics

Results 99 comments of Francesco Rizzi

array_t: overload `operator()` for multi-dim indexing

agreed, let me modify the PR

array_t: overload `operator()` for multi-dim indexing

@rwgk my bad for writing a description that was imprecise. My origianl main intent was to add `operator()` and when i said bounds was imprecise. I fixed the description now....

array_t: overload `operator()` for multi-dim indexing

CI failure is unrelated (failed to fetch boost)

array_t: overload `operator()` for multi-dim indexing

I actually used those before but I remember having some issues. Obviously now I don't remember off the top of my head the issues... but that was one of the...

array_t: overload `operator()` for multi-dim indexing

Btw I actually would have proposed a multi index subscript operator [] that would be intuitive and also equivalent to python syntax. https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2021/p2128r6.pdf I think that would probably be my...

array_t: overload `operator()` for multi-dim indexing

I understand all these viewpoints , but I like to point out that the proxies are (1) not intuitive (2) a deviation from any "linear algebra/container like" thing, and (3)...

support mixed fom/rom: default lspg and default implicit galerkin

this needs to be rebased and also reverified because even if it works, maybe is could be improved or simplified

adjacent_difference should not allow running with source being the same as destination

on https://en.cppreference.com/w/cpp/algorithm/adjacent_difference am i missing it or the precondition is not stated ?

adjacent_difference should not allow running with source being the same as destination

Yes right, I was just surprised the other part of the condition was missing

adjacent_difference should not allow running with source being the same as destination

I think what you highlight refers to what requirements "op" should have and so what it should do or not doto its arguments. How the result of op is used...