On 20 Oct 2025, at 19:34, Sergei Egorov <xxxxxx@acm.org> wrote: > Not to give an impression that I am fighting the prevailing opinion: > > after thinking about this issue for some time, I started to like the idea of introducing a companion form, match*, that specifies explicitly both left-to-right matching order and left-to-right nested scope for the pattern variables, making them immediately available for reference downstream from the place of their introduction (I would not go as far as specifying what will happen if you set! them -- they may have shadow copies). This would allow the intent of pattern users to be clearly visible at a quick glance. In my opinion, this form will be used rarely, and only in very specific circumstances, as an alternative to having a guard clause. Perhaps for some sort of tracing too? You will still need to prescribe somewhat more precisely what ‘left-to-right matching order and left-to-right nested scope’ means. Daphne
