Abstract naming stuff
Open
architectural
good first issue
- Dominant language
- Rust
- Stars
- 2.6k
- Forks
- 175
- PR merge metrics
- No merged PRs in 30d
Description
We should deal with names for functions, types and typedefs in a similar way, so that things like #494 are fixed for all of them. We should see what we can make uniform for the different analysis phases, maybe extracting to a new phase.
Contributor guide
Research direction
No files, tests, or entry points are named. Start by comparing how functions, types, and typedefs are named across the analysis phases, using issue #494 as the referenced case; done means a uniform naming approach is implemented for all three.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100