You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The docPrime linter uses the file scripts/nolints_prime_decls.txt to keep track of which primed declarations already existed when the linter was created and should not be flagged by the linter.
This works well for mathlib, but downstream projects get flooded by warnings when they build mathlib from scratch, instead of downloading the cache via lake exe cache get.
The reason is that the linter looks for the file in scripts/nolints_prime_decls.txt, does not find it in the downstream project and therefore complains about all primed declarations. Once the cache has been saved with the linter warnings, lake then replays it every time.
For this reason, the docPrime linter is now disabled in mathlib.
The
docPrime
linter uses the filescripts/nolints_prime_decls.txt
to keep track of which primed declarations already existed when the linter was created and should not be flagged by the linter.This works well for mathlib, but downstream projects get flooded by warnings when they build mathlib from scratch, instead of downloading the cache via
lake exe cache get
.The reason is that the linter looks for the file in
scripts/nolints_prime_decls.txt
, does not find it in the downstream project and therefore complains about all primed declarations. Once the cache has been saved with the linter warnings, lake then replays it every time.For this reason, the
docPrime
linter is now disabled in mathlib.See these previous Zulip discussions:
#20559 is the PR where the linter was disabled.
The text was updated successfully, but these errors were encountered: