Ligature request: `==~`
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 82k
- Forks
- 3.2k
- PR merge metrics
- No merged PRs in 30d
Description
We have now ligatures for =~ and !~.
But I miss a ligature for ==~.
In Groovy for example =~ is the "find" operator, building a regex matcher with the regex on the right applied to the string on the left and the matcher's Groovy truth is whether the regex matches somewhere within the string.
And ==~ is the "matches" operator, that returns whether the whole string on the left completely matches the regex on the right.
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 file or test is named. Start by locating the existing =~ and !~ ligature definitions, then inspect how a new ==~ ligature is represented and rendered. Done means the sequence renders as a ligature without changing the existing operators, including in Groovy examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- design
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100