`_check_sigspec` is slow
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.2k
- Forks
- 280
- Avg merge
- 6d 17h
- Merged PRs (30d)
- 4
Description
Hi, while optimizing some code I noticed an unreasonable amount of the time is spent in _check_sigspec. I suspect this is the heavy usage of inspect methods in curry code.
I think this is not justified as one can run inspect stuff once, and store for later.
Did anyone encounter this?
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 at _check_sigspec and its callers in the curry code, then profile representative curry usage to confirm whether repeated inspect calls dominate. Review the existing behavior around signature checking before changing how results are retained; done means preserving those checks while demonstrating that the slow path is measurably faster.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100