• Top
    • Documentation
    • Books
    • Boolean-reasoning
    • Projects
      • Apt
      • Zfc
      • Acre
      • Milawa
      • Smtlink
      • Abnf
      • Vwsim
      • Isar
      • Wp-gen
      • Dimacs-reader
      • Pfcs
      • Legacy-defrstobj
      • Proof-checker-array
      • Soft
      • C
      • Farray
      • Rp-rewriter
      • Instant-runoff-voting
      • Imp-language
        • Semantics
          • Step
          • Write-var
          • Outcome
            • Outcome-case
              • Outcome-fix
              • Outcome-equiv
              • Outcome-terminated
              • Outcomep
              • Outcome-nonterminating
              • Outcome-kind
            • Beval
            • Read-var
            • Config
            • Terminatingp
            • Aeval
            • Step*
            • Stepn
            • Env
          • Abstract-syntax
          • Interpreter
        • Sidekick
        • Leftist-trees
        • Java
        • Taspi
        • Bitcoin
        • Riscv
        • Des
        • Ethereum
        • X86isa
        • Sha-2
        • Yul
        • Zcash
        • Proof-checker-itp13
        • Regex
        • ACL2-programming-language
        • Json
        • Jfkr
        • Equational
        • Cryptography
        • Poseidon
        • Where-do-i-place-my-book
        • Axe
        • Bigmems
        • Builtins
        • Execloader
        • Aleo
        • Solidity
        • Paco
        • Concurrent-programs
        • Bls12-377-curves
      • Debugging
      • Std
      • Proof-automation
      • Macro-libraries
      • ACL2
      • Interfacing-tools
      • Hardware-verification
      • Software-verification
      • Math
      • Testing-utilities
    • Outcome

    Outcome-case

    Case macro for the different kinds of 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 outcome structure, or to split into cases based on its type.

    Short Form

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

    (outcome-case x :terminated)

    is essentially just a safer alternative to writing:

    (equal (outcome-kind x) :terminated)

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

    Long Form

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

    (outcome-case x
      :terminated ...
      :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 :terminated case, you can use fty::defprod-style foo.bar style accessors for x without having to explicitly add a terminated b* binder.