`glob_with` case insensitivity seems broken

Open
  • Is something wrong?
#61 1 comment 5 reactions 0 assignees View on GitHub

@RanaPriyansh is already working on this.

Since Sep 20, 2026.

  • #191 by @RanaPriyansh — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
tooling

Research direction

Start with MatchOptions and the match_with function, then reproduce the report using the globtest commands and the target/Target examples. Trace how case_sensitive is handled and add coverage for both true and false settings; done means case-sensitive matching distinguishes the names while case-insensitive matching finds target for Target.

Written by the indexing model from the issue text.

Description

In developing globtest (crate here), I seem to have run into an issue where the case_sensitive paremeter of MatchOptions is completely ignored in the match_with function.

Here's an example:

mqudsi@ZBook /m/c/U/M/g/globtest> globtest -d "*"

        options {
                case_sensitive: true,
                require_literal_leading_dot: true,
                require_literal_separator: true
        };

Cargo.lock
Cargo.toml
LICENSE
README.md
src
target

mqudsi@ZBook /m/c/U/M/g/globtest> globtest -d "target"

        options {
                case_sensitive: true,
                require_literal_leading_dot: true,
                require_literal_separator: true
        };

target

mqudsi@ZBook /m/c/U/M/g/globtest> globtest -id "Target"

        options {
                case_sensitive: false,
                require_literal_leading_dot: true,
                require_literal_separator: true
        };
Dominant language
Rust
Stars
597
Forks
97
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rust-lang/glob

All issues in rust-lang/glob

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.