• Top
    • Documentation
    • Books
    • Boolean-reasoning
    • Projects
      • Apt
      • Zfc
      • Acre
      • Milawa
      • Smtlink
      • Abnf
      • Vwsim
      • Isar
      • Pfcs
      • Wp-gen
      • Dimacs-reader
      • Legacy-defrstobj
      • Proof-checker-array
      • Soft
      • C
      • Farray
      • Rp-rewriter
      • Instant-runoff-voting
      • Imp-language
      • Sidekick
      • Leftist-trees
      • Java
      • Taspi
      • Riscv
      • Bitcoin
      • Des
      • Ethereum
      • X86isa
      • Sha-2
      • Yul
      • Zcash
      • Proof-checker-itp13
      • Regex
      • ACL2-programming-language
        • Primitive-functions
        • Translated-terms
        • Values
        • Evaluation
          • Step-from-trans
          • Call-primitive-function
          • Step-from-init
          • Put-leftmost-nonconst
          • Exec-outcome
            • Exec-outcome-case
              • Exec-outcome-fix
              • Exec-outcome-equiv
              • Exec-outcome-p
              • Exec-outcome-terminating
              • Exec-outcome-nonterminating
              • Exec-outcome-kind
              • Exec-outcome-error
            • Stepn
            • Step
            • Terminatingp
            • Get-leftmost-nonconst
            • Exec-call
            • Step*
          • Program-equivalence
          • Functions
          • Packages
          • Programs
          • Interpreter
          • Evaluation-states
        • Json
        • Jfkr
        • Equational
        • Cryptography
        • Poseidon
        • Where-do-i-place-my-book
        • Axe
        • Aleo
        • Bigmems
        • Builtins
        • Execloader
        • Solidity
        • Paco
        • Concurrent-programs
        • Bls12-377-curves
      • Debugging
      • Std
      • Community
      • Proof-automation
      • ACL2
      • Macro-libraries
      • Interfacing-tools
      • Hardware-verification
      • Software-verification
      • Math
      • Testing-utilities
    • Exec-outcome

    Exec-outcome-case

    Case macro for the different kinds of exec-outcome structures.

    This is an ACL2::fty sum-type case macro, typically introduced by fty::defflexsum or fty::deftagsum. It allows you to safely check the type of a exec-outcome structure, or to split into cases based on its type.

    Short Form

    In its short form, exec-outcome-case allows you to safely check the type of a exec-outcome structure. For example:

    (exec-outcome-case x :terminating)

    is essentially just a safer alternative to writing:

    (equal (exec-outcome-kind x) :terminating)

    Why is using exec-outcome-case safer? When we directly inspect the kind with equal, there is no static checking being done to ensure that, e.g., :terminating is a valid kind of exec-outcome structure. That means there is nothing to save you if, later, you change the kind keyword for this type from :terminating to something else. It also means you get no help if you just make a typo when writing the :terminating symbol. Over the course of developing VL, we found that such issues were very frequent sources of errors!

    Long Form

    In its longer form, exec-outcome-case allows you to split into cases based on the kind of structure you are looking at. A typical example would be:

    (exec-outcome-case x
      :terminating ...
      :error ...
      :nonterminating ...)

    It is also possible to consolidate ``uninteresting'' cases using :otherwise.

    For convenience, the case macro automatically binds the fields of x for you, as appropriate for each case. That is, in the :terminating case, you can use fty::defprod-style foo.bar style accessors for x without having to explicitly add a terminating b* binder.