[1.0] Change `MatchOptions::default` to match `MatchOptions::new`
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 595
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
Description
The Default trait implementation can call new. new could become const.
We don't really need new if we have default, but I think it's fine to keep.
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
Start at src/lib.rs around lines 1084-1091 and compare the MatchOptions::default and MatchOptions::new implementations. Confirm the default implementation delegates to new, consider the noted const possibility, and run the repository's existing tests to verify behavior is unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100