.. :: module language.safe-agda where .. _safe-agda: ********* Safe Agda ********* By using the option :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 :option:`--safe` is incompatible with: * ``postulate``; can be used to assume any axiom. * :option:`--allow-unsolved-metas`; forces Agda to accept unfinished proofs. * :option:`--allow-incomplete-matches` and pragma :ref:`NON_COVERING `; allows to prove false using a partial function or through a partial proof. * :option:`--no-positivity-check` and pragmas :ref:`NO_POSITIVITY_CHECK ` and :ref:`POLARITY `; make it possible to write non-terminating programs via datatypes that are not strictly positive. * :option:`--no-termination-check` and pragmas :ref:`TERMINATING ` and :ref:`NON_TERMINATING `; give loopy programs any type. * pragma :ref:`NO_UNIVERSE_CHECK `; allows the user to encode the Girard-Hurken paradox. * pragma :ref:`INJECTIVE `; allows to prove false by declaring a non-injective function as injective. * pragma :ref:`ETA `; can be used force eta-equality for unguarded recursive records which can make Agda loop. * :option:`--allow-exec`; allows system calls during type checking. * :option:`--no-load-primitives`; allows the user to bind the sort and level primitives manually. The option :option:`--safe` is coinfective (see :ref:`consistency-checking-options`); if a module is declared safe, then all its imported modules must also be declared safe.