TypeCheck should be an abstraction
Open
Nobody has claimed this yet.
enhancement
good first issue
- Dominant language
- Python
- Stars
- 53
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Currently, there are strong dependencies between several classes and the type checking. This should be an abstraction handled through composition and probably decorator.
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 by locating the TypeCheck implementation and the classes with strong dependencies on type checking. Read how those classes invoke or own type-checking behavior, then map the composition or decorator boundary described in the issue. Done means type checking is handled through a clear abstraction with the existing dependent classes using it consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100