min:max indexing does not support SoA but does not prevent this at compile time? about stan HOT 5 CLOSED

Indexing into an SOA matrix should be efficient, so it shouldn't be too expensive to create the non-SOA matrix x[1:M]. Then we can assign it to the SOA matrix y, we just need the chain() on the SOA data type to add all the adjoints of y to the adjoints of x. Not super efficient, but it shouldn't be dreadful.

from stan.

That's odd, it should work. Let me look at this today it sounds like a bug in the rvalue function for min max indexing

from stan.

I just opened another issue on Math, but worth noting here that replacing the indexing with a call to head or segment also leads to failure (though in that case, it is a segfault rather than junk inference)

from stan.

Okay yeah digging into this it's an issue in the math library. I'm going to put up a PR in a minute

from stan.

Closing as this was a bug in math

from stan.