Skip to content

Clarify double asterisk behaviour - #65

Closed
jamiecobbett wants to merge 1 commit into
gobwas:masterfrom
jamiecobbett:clarify-double-asterisk-behaviour
Closed

Clarify double asterisk behaviour#65
jamiecobbett wants to merge 1 commit into
gobwas:masterfrom
jamiecobbett:clarify-double-asterisk-behaviour

Conversation

@jamiecobbett

Copy link
Copy Markdown

I did not understand what "super-asterisk" means, and I had naively assumed that the behaviour would match glob implementations I am used to.

If there's anything that was described in the existing copy that I've missed, please let me know.

Thanks for making this library 👍

I did not understand what "super-asterisk" means, and I had naively assumed
that the behaviour would match glob implementations I am used to.
gobwas added a commit that referenced this pull request Aug 28, 2026
The regexps in BenchmarkCompareGlobAndRegexp now carry the `s` flag and
escaped dots, so they are the exact equivalents of the globs; refresh
both tables from a single run. Explain that `**` is not the shells'
globstar and add an Escaping section (backslashes in Go string
literals).

Fixes: #21, #35, #38, #58, #65
@gobwas

gobwas commented Aug 28, 2026

Copy link
Copy Markdown
Owner

The readme was rewritten as part of v1 (#73, now merged) and covers this -- ** is documented as not being the shells' globstar. Thanks!

@gobwas gobwas closed this Aug 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants