A regex pattern is a regex literal, representing a test that the subject, when stringified, successfully matches the regex.
Is this privileging literals in such a way that when /.../ can act differently than when re after re = /.../ in an environment where primordials have been subject to arbitrary manipulation?
It does include clarifying text:
(Technically, this just invokes the RegExp.prototype[Symbol.customMatcher] method; that is, x is /foo/; and let re = /foo/; x is re; are identical in behavior wrt built-in fiddling.)
(originally posted by @gibson042 in https://github.com/tc39/proposal-pattern-matching/pull/293#discussion_r1311844389)
https://github.com/tc39/proposal-pattern-matching#regex-patterns
It does include clarifying text:
...but the initial sentence is still misleading.
The section's "Examples" block is also empty.