microsoft / microsoft/debug-adapter-protocol
GotoTarget lifetime
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.8k
- Forks
- 173
- Avg merge
- 7d 7h
- Merged PRs (30d)
- 2
Description
The specification does not define the lifetime of a GotoTarget as obtained from a given GotoTargetsRequest, so it is unclear if it's legal for an IDE to cache them and reuse them later (possibly across goto, across continue, or in different frames that just happen to use the same source), or whether the adapter can clean up associated resources more aggressively - e.g. on invalidate them on every goto.
It's also unclear whether the adapter can return different IDs for the same file/line on a subsequent request, even if it ensures that old IDs are still valid to use in goto - and if it can do so, then how should the IDE interpret this.
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.
Research direction
Start by reviewing the protocol specification sections for GotoTargetsRequest, GotoTarget, and goto. Resolve whether targets may be cached across requests, goto operations, continues, or frames, and whether IDs may change; document the adapter and IDE obligations so the lifetime and identifier behavior are unambiguous.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100