`import runtime NonsenseModule` emits no diagnostics
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 9.2k
- Forks
- 990
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 175
Description
Prerequisites
Please put an X between the brackets as you perform the following steps:
- Check that your issue is not already filed:
https://github.com/leanprover/lean4/issues - Reduce the issue to a minimal, self-contained, reproducible test case.
Avoid dependencies to Mathlib or Batteries. - Test your test case against the latest nightly release, for example on
https://live.lean-lang.org/#project=lean-nightly
(You can also use the settings there to switch to “Lean nightly”)
Description
import runtime NonsenseModule succeeds even when NonsenseModule.lean does not exist
Context
I am investigating whether there is infrastructure to have dependencies which are only used at compile-time, and don't end up initialized in compiled binaries.
Steps to Reproduce
- Create
test.leanwithimport runtime NonsenseModule - Open it with VSCode
- Build it with `lake build
- Run
lake env lean --deps test.lean
Expected behavior: Steps 2, 3, and 4 all fail because the module doesn't exist
Actual behavior: Only step 4 fails.
Versions
4.12.0
Additional Information
Impact
Add 👍 to issues you consider important. If others are impacted by this issue, please ask them to add 👍 to it.
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 with the minimal test.lean containing import runtime NonsenseModule, then reproduce the behavior in VSCode, with lake build, and with lake env lean --deps test.lean. Trace how import runtime is handled across these paths; done means the missing module is diagnosed consistently by all three steps.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100