@robby I think I’ve seen ...+ in papers

I may have too. It doesn’t seem that common tho.

Speaking of which should we maybe add ...+ (as an alias for ..1) to racket/match?

I’ve had a few dummy moments where I’ve worked with syntax/parse for awhile… then try to use ...+ with match. And because ...+ is a valid identifier the error message is just “no matching pattern” — or worse maybe it does match, somehow.

@greg Definitely open an issue for that, seems like an easy usability win

I think that’s technically not backwards compatible, but I can’t imagine anyone would intentionally bind ...+ as an identifier.

Oh dang you’re right about compatibility.

Although I wouldn’t pick ...+ as an identifier, I try to use lots of Morse code identifiers like ...___.... Teammates love that! ¯_(ツ)_/¯