I was bitten pretty hard (my fault!) by a subtle difference in eXtended mode's handling of spaces in character classes. I was expecting (except in a much more complicated context) (?x)[ ] to match a single space as it does with pcre2, but that does not seem to be the case (and doesn't seem to be documented?).

In PCRE2, (?x) enables spurious use of whitespace everywhere except in character c

Ideas:

• Set a minimum dimension for images.
• Find a way to detect dimensions before downloading the image.

Please add VB/VBA to your language list.

In the readme file of the raspberry and django project change python2.7 to python3.7
It is causing lots of problem

[$value, $unit] = pattern('(\d+)[cm]m')->match('13cm')->tuple(1, 2)->first();

$value // '14'
$unit // 'cm'

Of course it should throw for invalid groups, nonexistent groups and unmatched groups.

Ideally, it should be similar to

[$value, $unit] = pattern('(\d+)[cm]m')->match('13cm')->first(function (Match $match) {
  return [$match->get(1), $match->get(2)];
});
``

• Basics Not applicable
• Character Classes
• Character Escapes Not applicable
• Escapes
• Groups
• Repetition
• Alternation
• Anchors
• Lookaround

I have been thinking how to organize package documentation. We basically have a few "groups" of functions that may make sense to be introduced together (at least in pkgdown):

Single-character functions

These are functions that return one character and do not require any "wrappers"

• rx_alpha_num
• rx_br and rx_line_break
• rx_digit
• rx_something
• rx_space
• rx_tab

Named capture groups have been requested as a feature here: https://www.reddit.com/r/rust/comments/djv01f/z/f48r5ao

Should not be too hard to implement:

First, extend parser to parse named groups. Store it in a HashMap<String, usize>.

Then add API to look up named groups using the name. Use the HashMap to look up the group index first.

Referencing named groups in backrefs doesn't h

Do you want to request a feature or report a bug?
Feature.

What is the current behavior?
The Playground's full sentence is quite long to read and the ending question is useless. Besides, it does not help to understand the table result shown right below this sentence.
_Let‘s write
a [global or not] regex
verifying that the text
[type your text here]
does
[contain|start with|end w