# Concatenation in the @select-based future

**URL:** https://discourse.flucoma.org/t/concatenation-in-the-select-based-future/1439
**Category:** Usage Questions
**Created:** [May 9, 2022, 4:32pm UTC](https://discourse.flucoma.org/t/concatenation-in-the-select-based-future/1439 "2022-05-09T16:32:54Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![rodrigo.constanzo](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/rodrigo.constanzo/32/12_2.png) [@rodrigo.constanzo](https://discourse.flucoma.org/u/rodrigo.constanzo)
#### Post date: [May 9, 2022, 6:08pm UTC](https://discourse.flucoma.org/t/concatenation-in-the-select-based-future/1439/4 "2022-05-09T18:08:09Z")

</div>

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 `deststartframe`s all over the place (that all break if you change anything upstream)?

---

_[View the full topic](https://discourse.flucoma.org/t/concatenation-in-the-select-based-future/1439)._