carp-dk / carp-dk/detekt-verify-implementation

Cache classes which have already been verified as immutable.

Open
#5 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Kotlin
Stars
7
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Verifying immutability is recursive. In case of type composition, very often the same types will need to be verified.

Therefore, a straightforward performance improvement is to cache the outcome of classes that have already been verified as immutable (or not).

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the recursive immutability verification entry point and tracing where composed types are checked repeatedly. Add caching for both immutable and non-immutable outcomes, then verify that repeated type checks reuse the result without changing verification behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.