fix: detect TOML lean_lib modules for nanoda - #168
Conversation
|
I just came across this PR and I was thinking, what about having the module name configurable? The use case: a project where only part of it should be checked by nanoda. For example, a "clean" mathematical part (should be checked) and an algorithmic/monadic/native_decide-heavy part. |
|
I think that the |
Created a separate issue for it: #179 |
|
Rebased onto current |
|
Updated this branch so the four changed files are current-
GitHub still marks the PR |
|
Closing in favor of #187. |
This PR fixes nanoda module discovery for current Lake TOML projects.
lake init name .tomlemits a top-level package name and a distinct[[lean_lib]]module name. The nanoda runner previously searched only for a legacy[package]section and failed before independent checking. Reading the package name alone would also be incorrect when its spelling differs from the Lean module root.The detector now prefers the first
lean_libname and retains the old first-name fallback for compatibility. A functional test generates a standard TOML package and requires the nanoda status to beSUCCESSwithsorryAxdisabled.