# Behavioural differences in \`match\` for splicing/single pattern variables

**URL:** <https://racket.discourse.group/t/behavioural-differences-in-match-for-splicing-single-pattern-variables/3571>\
**Category:** Questions & Answers\
**Created:** [February 16, 2025, 9:25pm UTC](https://racket.discourse.group/t/behavioural-differences-in-match-for-splicing-single-pattern-variables/3571 "2025-02-16T21:25:14Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![bakgatviooldoos](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/bakgatviooldoos/32/1381_2.png) [@bakgatviooldoos](https://racket.discourse.group/u/bakgatviooldoos)\
**Post date:** [February 17, 2025, 4:39pm UTC](https://racket.discourse.group/t/behavioural-differences-in-match-for-splicing-single-pattern-variables/3571/3 "2025-02-17T16:39:20Z")

</div>

> [@greghendershott](#):
>
> the source code might have a "TO-DO"

I remembered seeing [something similar](https://racket.discourse.group/t/using-match-ellipses-on-multiple-elements/2891) recently posted by @jbclements about `~seq`-like behaviour in `match`, which might be related to why this doesn't work, in general?

> [@greghendershott](#):
>
> I'm surprised that it prints a message to stderr

Right? I have only ever encountered these a handful of times--makes me feel like the code's broken the fourth wall, so to speak.

---

_[View the full topic](https://racket.discourse.group/t/behavioural-differences-in-match-for-splicing-single-pattern-variables/3571)._