Skip to content

Improving the cache of the declaration finder for external references #3919

Open
@bclothier

Description

@bclothier

From a discussion in chat, there is one spot where we could improve the cache. Currently when a project has more reference, it becomes more and more slower to parse because of # of declarations that must be analyzed and eventually resolved from the external references.

The proposal is to cache the declarations from external references and refresh only if the user has actually changed the references (which is a comparatively rare event) and the initial parse. That would help the performance in where a project references several external libraries.

Note that implementing this will be a challenge as the collections within the finder are loaded lazily and one must be careful to ensure that cache does not become stale.

Metadata

Metadata

Assignees

No one assigned

    Labels

    difficulty-04-quackheadDare?enhancementFeature requests, or enhancements to existing features. Ideas. Anything within the project's scope.resolverIssue is easier to resolve with knowledge of the internal resolver API and the Antlr4 parse trees.technical-debtThis makes development harder or is leftover from a PullRequest. Needs to be adressed at some point.up-for-grabsUse this label in conjunction with a difficulty level label, e.g. difficulty-02-ducky

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions