Add a test case about overriding the prelude #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is well known, but but without further protection against the
prelude
command, one can easily prove unsound things, as this testdemonstrates.
Until the kernel itself is guarded against this (tracked at
leanprover/lean4#188), I wonder if
lean4checker
should havea defense, and warn if
prelude
is used, or something along these lines?I had to restructure the tests into their own library with a
glob
, asimporting this file from another file that also imports the normal
prelude seems to fail with