Safe Agda¶
By using the option --safe (as a pragma option, or on the
command-line), a user can specify that Agda should ensure that
features leading to possible inconsistencies should be disabled.
Here is a list of the features --safe is incompatible with:
postulate; can be used to assume any axiom.--allow-unsolved-metas; forces Agda to accept unfinished proofs.--allow-incomplete-matchesand pragma NON_COVERING; allows to prove false using a partial function or through a partial proof.--no-positivity-checkand pragmas NO_POSITIVITY_CHECK and POLARITY; make it possible to write non-terminating programs via datatypes that are not strictly positive.--no-termination-checkand pragmas TERMINATING and NON_TERMINATING; give loopy programs any type.pragma NO_UNIVERSE_CHECK; allows the user to encode the Girard-Hurken paradox.
pragma INJECTIVE; allows to prove false by declaring a non-injective function as injective.
pragma ETA; can be used force eta-equality for unguarded recursive records which can make Agda loop.
--allow-exec; allows system calls during type checking.--no-load-primitives; allows the user to bind the sort and level primitives manually.
The option --safe is coinfective (see
Checking options for consistency); if a module is declared safe,
then all its imported modules must also be declared safe.