You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When hovering over the ? in ?_ you get the correct docstring for synthetic holes, but when hovering over the _ you get the docstring for normal holes which is not applicable here.
Steps to Reproduce
example : False := by
refine ?_
sorry
Paste the above code into the Lean web editor
Move the cursor on top of the underscore
Expected behavior: Docstring for synthetic holes is shown
Actual behavior: Docstring for normal holes is shown
in principle we'd like to use the existing parser
```
"?" >> (ident <|> hole)
```
but somehow annotate it so that hovering the `hole` will not show the
hole's hover. But for now it was easier to just change the parser to
```
"?" >> (ident <|> "_")
```
and be done with it.
Fixes#5021
in principle we'd like to use the existing parser
```
"?" >> (ident <|> hole)
```
but somehow annotate it so that hovering the `hole` will not show the
hole's hover. But for now it was easier to just change the parser to
```
"?" >> (ident <|> "_")
```
and be done with it.
Fixes#5021
Prerequisites
Please put an X between the brackets as you perform the following steps:
https://github.com/leanprover/lean4/issues
Avoid dependencies to Mathlib or Batteries.
https://live.lean-lang.org/#project=lean-nightly
(You can also use the settings there to switch to “Lean nightly”)
Description
When hovering over the
?
in?_
you get the correct docstring for synthetic holes, but when hovering over the_
you get the docstring for normal holes which is not applicable here.Steps to Reproduce
Expected behavior: Docstring for synthetic holes is shown
Actual behavior: Docstring for normal holes is shown
Versions
4.12.0-nightly-2024-08-13
on live.lean-lang.orgImpact
Add 👍 to issues you consider important. If others are impacted by this issue, please ask them to add 👍 to it.
The text was updated successfully, but these errors were encountered: