Improve `SyntaxError` suggestions for common operator typos and cross-language mistakes
Open
Nobody has claimed this yet.
interpreter-core
topic-parser
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
As I proposed in #151129 (comment), we can also add suggestions for
<>("not equal" in Pascal and Python 2), "=<", "=>" and "=!" (typo in "<=", ">=" and "!="), "===" ("is" in JavaScript and PHP).
suggested by @serhiy-storchaka
"===" ("is" in JavaScript and PHP).
And Mathematica.
follow up #150906
I'll submit a PR for this . shortly
Linked PRs
- gh-151375
Contributor guide
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 by reviewing the discussion in #150906 and the linked gh-151375 PR, then trace the existing SyntaxError suggestion behavior for the listed operator typos. Done means the requested cross-language and mistyped-operator suggestions are covered consistently, with corresponding tests if they are part of the existing change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100