lean-ja / lean-ja/lean-by-example
ダブルバッククォートは、後に term が続くことを期待している
Open
Nobody has claimed this yet.
構文・パーサ
- Dominant language
- Lean
- Stars
- 188
- Forks
- 15
- Avg merge
- 9h 8m
- Merged PRs (30d)
- 6
Description
local macro "baz" : term => ``(fun x => x)
-- タクティクだとだめ
/-
unexpected token '('; expected identifier
-/
local macro "my_exfalso" : tactic => ``(tactic| apply False.elim)
-- ダブルバッククォートの後には term が来ると思われているっぽい
/-
unexpected token '#eval'; expected term
-/
local macro "my_check" : command => ``(#eval my_exfalso)
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 reproducing the Lean snippets in the issue, comparing double-backtick expansion in term, tactic, and command positions. Determine whether the examples reflect an issue in this repository or expected Lean behavior; done should include a confirmed diagnosis and a clearly scoped follow-up.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100