Skip to content

Allow legacy workspaces to import module-system dependencies - #11

Merged
kim-em merged 1 commit into
mainfrom
fix/legacy-workspace-dependencies
Sep 28, 2026
Merged

kim-em merged 1 commit into
mainfrom
fix/legacy-workspace-dependencies

Conversation

@kim-em

@kim-em kim-em commented Sep 28, 2026

Copy link
Copy Markdown
Collaborator

Generated workspaces use legacy Lean files. Importing a solution dependency that declares requiresModuleSystem currently emits a Lake warning, while adding a module header breaks imports of the generated legacy helpers.

Declare allowNonModules = true in generated package configurations, using Lake’s explicit compatibility setting. This preserves the existing visibility rules and permits module-system dependencies without changing statement-import restrictions or disabling other warnings.

Validation: the generator and Lean dependency/module-path tests pass without warnings on Lean 4.33; the CLI contract test now builds a legacy solution against a local Git dependency using the module system. A cold, sandboxed LeanEval workspace importing LeanPool passes without warnings on Lean 4.35.0-rc3.

@kim-em
kim-em merged commit 0b8cc2d into main Sep 28, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant