We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If I hide the Law of Excluded Middle in a custom block, I'm able to use it in earlier levels which would also allow a proof without LEM.
To reproduce, wrap ((A→ ⊥) → ⊥) → A in a custom block and use it in the (((A → ⊥) → ⊥ ) → ⊥) → (A → ⊥) level.
The text was updated successfully, but these errors were encountered:
On a related note, I want to able to find out which axioms were assumed when constructing a block.
Sorry, something went wrong.
If you are cheating, you are only cheating yourself :-)
I’m aware of this; the various levels just very thinly hide the additional basic rules, but the underlying logic is mostly the same.
I guess it would make sense for the system to track which axioms were used in each basic block, and gray out those not available in a certain task.
Do the blocks remember their content, or is that forgotten, once the block is “compiled”?
Right now, they are forgotten, but that is not necessary the final design.
No branches or pull requests
If I hide the Law of Excluded Middle in a custom block, I'm able to use it in earlier levels which would also allow a proof without LEM.
To reproduce, wrap ((A→ ⊥) → ⊥) → A in a custom block and use it in the (((A → ⊥) → ⊥ ) → ⊥) → (A → ⊥) level.
The text was updated successfully, but these errors were encountered: