Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support lazy resolving of TypeHierarchyItem properties #132115

Closed
gjsjohnmurray opened this issue Sep 2, 2021 · 1 comment
Closed

Support lazy resolving of TypeHierarchyItem properties #132115

gjsjohnmurray opened this issue Sep 2, 2021 · 1 comment
Assignees
Labels
*out-of-scope Posted issue is not in scope of VS Code typehierarchy under-discussion Issue is under discussion for relevance, priority, approach

Comments

@gjsjohnmurray
Copy link
Contributor

For example, it may be expensive to compute the range of a TypeHierarchyItem being returned by provideTypeHierarchySubtypes

Relates to #15533

@jrieken jrieken added typehierarchy under-discussion Issue is under discussion for relevance, priority, approach labels Sep 3, 2021
@jrieken jrieken added the *out-of-scope Posted issue is not in scope of VS Code label Dec 5, 2022
@vscodenpa
Copy link

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding, and happy coding!

@vscodenpa vscodenpa closed this as not planned Won't fix, can't repro, duplicate, stale Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
*out-of-scope Posted issue is not in scope of VS Code typehierarchy under-discussion Issue is under discussion for relevance, priority, approach
Projects
None yet
Development

No branches or pull requests

3 participants