Automattic / Automattic/harper

Flag "equal to" where "equal is used as a verb"

Open
#2,697 0 comments 0 reactions 0 assignees View on GitHub
enhancement grammar harper-core linting
Dominant language
Rust
Stars
15.4k
Forks
627
Avg merge
1d 15h
Merged PRs (30d)
102

Description

I just heard "to equal to" in a YouTube video. Googling shows that it's a common class of error.

"Equal" is both an adjective and a verb but "to" is only used with the adjective:
- ✅ A equals B
- ✅ A is equal to B
- ❌ A equals to B

Here's some examples from GitHub:
- ` ` should **equal to** `' '` (one space)
- the local_frame will **equal to** the initial frame
- one cycle would **equal to** 0.27ns that would mean a branch miss would be 4.05ns
- update the variable to **equal to** sum of internal cluster distances
- repeat `posterior::split_chains` on the fitted object until these **equal to** the number of cores wanted
- I am wondering here, why does the `num_qps_per_rank` need to **equal to** the number of local experts?
- Which does **equal to** 0.

Contributor guide

Open the contributing guide

Research direction

No file, test, or entry point is named in the issue. Start by locating the existing grammar-rule implementation and its test conventions, then verify that the rule flags verb uses such as “equals to” while leaving adjective uses such as “is equal to” valid.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.