spring-projects / spring-projects/spring-tools
[spring index] optimize super type information for beans with hash codes instead of strings
@martinlippert is already working on this.
Since May 10, 2023.
- Dominant language
- Java
- Stars
- 983
- Forks
- 240
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 7
Description
The only purpose of keeping all the super types of a bean type within the spring index is to check for type compatibility. This could be optimized in a way to not store the fully qualified type information as strings in the index storage, but hash codes only (and then compare hash codes instead of type strings).
While this seems to be straight forward and easy to do, we need to verify that this covers all the ways a bean is being found when looking for a compatible bean. Generics might be a potential complicated case here, but we need to double check while implementing this optimization here.
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.
Assessment
This issue has not been assessed yet.