This PR fixes an issue where go-to-definition would jump to the wrong location in presence of async theorems. While the elaborator does not explicitly depend on `FVar`s not being reused between declarations, the language server turned out to do so. As we would have to split the name generator in any case as soon as we add any parallelism within proofs, we now do so for any async code in order to uphold this invariant again. --------- Co-authored-by: mhuisi <mhuisi@protonmail.com>
26 lines
783 B
Text
26 lines
783 B
Text
{"textDocument": {"uri": "file:///compHeader.lean"},
|
|
"position": {"line": 2, "character": 22}}
|
|
{"items":
|
|
[{"label": "veryLongNam",
|
|
"kind": 6,
|
|
"data": ["«external:file:///compHeader.lean»", 2, 22, 0, "f_uniq.11"]},
|
|
{"label": "veryLongNameForCompletion",
|
|
"kind": 21,
|
|
"data":
|
|
["«external:file:///compHeader.lean»",
|
|
2,
|
|
22,
|
|
0,
|
|
"cveryLongNameForCompletion"]}],
|
|
"isIncomplete": false}
|
|
Resolution of veryLongNam:
|
|
{"label": "veryLongNam",
|
|
"kind": 6,
|
|
"detail": "Sort u_1",
|
|
"data": ["«external:file:///compHeader.lean»", 2, 22, 0, "f_uniq.11"]}
|
|
Resolution of veryLongNameForCompletion:
|
|
{"label": "veryLongNameForCompletion",
|
|
"kind": 21,
|
|
"detail": "Type",
|
|
"data":
|
|
["«external:file:///compHeader.lean»", 2, 22, 0, "cveryLongNameForCompletion"]}
|