Writing becomes laggy when there are many strokes/paths.
Open
- Dominant language
- Kotlin
- Stars
- 360
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Description
When there are many strokes/paths, writing again causes noticeable lag. Can this be optimized?
Contributor guide
Research direction
The issue names no file, test, or entry point. Start by reproducing the lag with many strokes, then trace the writing path to identify the relevant performance bottleneck; done means writing remains responsive with a large number of strokes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100