Implement a check when float-only operations are used
Open
Nobody has claimed this yet.
feature
- Dominant language
- Python
- Stars
- 20.6k
- Forks
- 3.3k
- PR merge metrics
- PR metrics pending
Description
Feature
Implement a new check that emits an error when the following conditions are met:
- A name is typed as
builtins.float - No runtime cast (
the_name = float(the_name)) on that name is done - A float-only attribute (like
builtins.float.hex) on that name is used
This can also be extended for when the builtins.complex.__complex__ attribute (or other complex-only attributes) is used on a builtins.complex-typed name without a runtime cast.
Pitch
This document explains the whole problem.
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
The issue names no files, tests, or entry points; begin with the linked float/complex problem document and trace the type-checker handling for float-only attributes. Done means an error is emitted for the stated uncast float case, with the complex extension addressed only if supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100