leanprover / leanprover/lean4

`import runtime NonsenseModule` emits no diagnostics

Open
#5,867 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug P-low
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:

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
  1. Create test.lean with import runtime NonsenseModule
  2. Open it with VSCode
  3. Build it with `lake build
  4. 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

Related Zulip thread

Impact

Add 👍 to issues you consider important. If others are impacted by this issue, please ask them to add 👍 to it.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.