Ability to opt out of `**` (have it behave like `*` / POSIX glob)
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 595
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
Description
I'm parsing a file format which uses glob patterns in C. The C glob function on unix does not support **. Instead, a series of consecutive * is the same as writing just one *
demonstrated with a posix shell:
$ ls -ld /usr/**/
drwxr-xr-x 2 root root 77824 Mar 19 16:34 /usr/bin/
drwxr-xr-x 2 root root 4096 Mar 19 09:05 /usr/games/
drwxr-xr-x 4 root root 4096 Nov 29 14:17 /usr/i686-w64-mingw32/
drwxr-xr-x 108 root root 20480 Mar 18 14:23 /usr/include/
drwxr-xr-x 118 root root 4096 Mar 19 16:34 /usr/lib/
drwxr-xr-x 3 root root 4096 Mar 11 09:31 /usr/lib64/
drwxr-xr-x 21 root root 12288 Mar 19 09:32 /usr/libexec/
drwxr-xr-x 12 root root 4096 Feb 19 09:37 /usr/local/
drwxr-xr-x 2 root root 20480 Mar 19 09:32 /usr/sbin/
drwxr-xr-x 347 root root 12288 Mar 19 16:34 /usr/share/
drwxr-xr-x 6 root root 4096 Mar 13 10:14 /usr/src/
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are identified in the issue. Start by tracing the public glob-matching entry point and its handling of consecutive *; define the opt-out behavior against the POSIX example, then add focused coverage showing ** behaves like * when opted out.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100