leanprover-community / leanprover-community/LeanSearchClient
`#loogle` command's unexpected behavior when used with `#guard_msgs`
Open
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 36
- Forks
- 13
- Avg merge
- 3m
- Merged PRs (30d)
- 4
Description
This raise no error.
import LeanSearchClient.LoogleSyntax
/--
info: Loogle Search Results
• #check Option.get!
-/
#guard_msgs in
#loogle Option ?a → ?a, "get!"
But this fails.
import LeanSearchClient.LoogleSyntax
/--
info: Loogle Search Results
• #check Option.get!
-/
#guard_msgs in
#loogle Option ?a → ?a, "get!"
/- hello -/
Contributor guide
No contributing guide indexed for this repository
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 reproducing the two examples using the LeanSearchClient.LoogleSyntax import, comparing #loogle inside #guard_msgs with and without the trailing comment. Inspect the interaction between these two command entry points; done means both examples behave consistently and the intended diagnostic is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100