microsoft/language-server-protocol

Call hierarchies, more info needed

Open

#1,219 opened on Mar 11, 2021

View on GitHub
 (0 comments) (1 reaction) (0 assignees)HTML (12,810 stars) (956 forks)batch import
clarificationhelp wanted

Description

When I read the 3.16 information about call hierarchies, I am left scratching my head. Is this mechanism all about finding out who calls or is called by a symbol (the cursor is placed on)?

The first question that pops up is how would this work in a functional language where a caller or callee is a piece of runtime data?

Second question is, given a cursor on the middle of the "print" call reference of the proverbial hello world program, what should the various call hierarchy requests do?

Might be very useful to provide examples or cite references to further explain what the LSP designers are trying to accomplish/achieve with this mechanism.

Contributor guide

Tech stack
None
Domain
documentationdeveloper experience
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
understanding of LSPknowledge of call hierarchy concept
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Review the LSP specification for call hierarchy (e.g., textDocument/prepareCallHierarchy and textDocument/callHierarchyIncomingCalls). Provide examples in a functional language like Haskell or Scheme. Consider referencing existing implementations or proposals. Write a clear explanation with code snippets.
Call hierarchies, more info needed · microsoft/language-server-protocol#1219 | Good First Issue