Running `tests/lean/run/treemap.lean` with `-D Elab.async=false` causes errors
Open
Nobody has claimed this yet.
bug
P-medium
- Dominant language
- Lean
- Stars
- 9.2k
- Forks
- 990
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 175
Description
On c2876a1a, running
time build/release/stage1/bin/lean tests/lean/run/treemap.lean -D Elab.async=false
gives errors like this:
tests/lean/run/treemap.lean:550:0: warning: declaration uses 'sorry'
⟨2, 4⟩
tests/lean/run/treemap.lean:549:0: error: ❌️ Docstring on `#guard_msgs` does not match generated message:
warning: declaration uses 'sorry'
---
info: ⟨2, 4⟩
tests/lean/run/treemap.lean:558:0: warning: declaration uses 'sorry'
(2, 4)
tests/lean/run/treemap.lean:557:0: error: ❌️ Docstring on `#guard_msgs` does not match generated message:
warning: declaration uses 'sorry'
---
info: (2, 4)
tests/lean/run/treemap.lean:606:0: warning: declaration uses 'sorry'
2
tests/lean/run/treemap.lean:605:0: error: ❌️ Docstring on `#guard_msgs` does not match generated message:
warning: declaration uses 'sorry'
...
These errors do not occur without -D Elab.async=false.
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
Run the command shown against tests/lean/run/treemap.lean with -D Elab.async=false and compare it with the default run. Inspect the #guard_msgs cases around lines 549-606 and the related elaboration or message-ordering entry points. Done means the treemap test passes in both async modes without mismatched generated messages.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100