# COMPOSE of TUPLE! and PATH! (and toplevel GROUP!)

**URL:** <https://revolt.metaeducation.com/forum/t/compose-of-tuple-and-path-and-toplevel-group/2056>\
**Category:** Feature Discover\
**Created:** [October 19, 2023, 6:39am UTC](https://revolt.metaeducation.com/forum/t/compose-of-tuple-and-path-and-toplevel-group/2056 "2023-10-19T06:39:14Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![hostilefork](https://revolt.metaeducation.com/forum/user_avatar/revolt.metaeducation.com/hostilefork/32/421_2.png) [@hostilefork](https://revolt.metaeducation.com/forum/u/hostilefork)\
**Post date:** [October 1, 2024, 2:02pm UTC](https://revolt.metaeducation.com/forum/t/compose-of-tuple-and-path-and-toplevel-group/2056/3 "2024-10-01T14:02:33Z")

</div>

With changes to things like SET-GROUP [becoming a CHAIN!](https://revolt.metaeducation.com/forum/t/introducingnew-chain-datatype/2226), we now have a situation where we are getting this behavior:

```
>> var: $x

>> compose [(var): 10]
== [(var): 10] ; hm, no substitution?

```

So this would see the **`(var): 10`** as a subsequence and require **`:DEEP`**.

_But I don't think DEEP should be necessary for this._ So I imagine that sequences are considered to be part of the same level for the purposes of COMPOSE'ing.

> [@hostilefork](#):
>
> And if you remember that TUPLE! can be nested underneath PATH! (not vice versa) then you can COMPOSE/DEEP and handle mixed tuples and paths:
> 
> ```plaintext
> >> compose/deep $(10 + 20)/a/b.(spread [c d e])
> == 30/a/b.c.d.e
> 
> ```

By that rule, I would imagine this would not require DEEP either.

---

_[View the full topic](https://revolt.metaeducation.com/forum/t/compose-of-tuple-and-path-and-toplevel-group/2056)._
