Concatenation in the @select-based future

That seems to work well, though it’s a whole lotta code for something that should (seemingly) “be easy”.

Having it as a native abstraction would be handy as, again, it would suck to have to find this thread to be able to do that with the package install etc…

I am curious on what @tremblap’s approach with this is, or what you guys have been doing in workshops when working with multiple descriptors. Surely that’s a use case that has come up a bunch already.

Do you just have a fixed set of descriptors/stats and pre-baked deststartframes all over the place (that all break if you change anything upstream)?