ec98c92ba6
This solves the issue where certain subexpressions are lacking syntax hovers because the hover text is not "builtin" - it only shows up if the `Parser` constant is imported in the environment. For top level syntaxes this is not a problem because `builtin_term_parser` will automatically add this doc information, but nested syntaxes don't get the same treatment. We could walk the expression and add builtin docs recursively, but this is somewhat expensive and unnecessary given that it's a fixed list of declarations in lean core. Moreover, there are reasons to want to control which syntax nodes actually get hovers, and while a better system for that is forthcoming, for now it can be achieved by strategically not applying the `@[builtin_doc]` attribute. Fixes #3842
8 lines
389 B
Text
8 lines
389 B
Text
{"textDocument": {"uri": "file:///hoverException.lean"},
|
|
"position": {"line": 2, "character": 14}}
|
|
{"range":
|
|
{"start": {"line": 2, "character": 7}, "end": {"line": 2, "character": 18}},
|
|
"contents":
|
|
{"value":
|
|
"Explicit binder, like `(x y : A)` or `(x y)`.\nDefault values can be specified using `(x : A := v)` syntax, and tactics using `(x : A := by tac)`.\n",
|
|
"kind": "markdown"}}
|