• Top
    • Documentation
    • Books
    • Boolean-reasoning
    • Projects
      • Apt
      • Zfc
      • Acre
      • Milawa
      • Smtlink
      • Abnf
      • Vwsim
      • Isar
      • Wp-gen
      • Dimacs-reader
      • Pfcs
      • Legacy-defrstobj
      • C
      • Proof-checker-array
      • Soft
      • Farray
      • Rp-rewriter
      • Instant-runoff-voting
      • Imp-language
      • Sidekick
      • Ethereum
      • Leftist-trees
      • Java
      • Riscv
      • Taspi
      • Bitcoin
      • Zcash
      • Des
      • X86isa
      • Sha-2
      • Yul
      • Proof-checker-itp13
      • Regex
      • ACL2-programming-language
      • Json
      • Jfkr
      • Equational
      • Cryptography
      • Axe
      • Poseidon
      • Where-do-i-place-my-book
      • Aleo
        • Aleobft
        • Aleovm
          • Circuits
          • Language
            • Grammar
            • Early-version
              • Abstract-syntax
                • Binary-op
                • Literal
                • Instruction
                • Hash-op
                • Literal-type
                • Operand
                • Unary-op
                • Identifier
                • Commit-op
                • Mapping
                • Function
                • Programdef
                • Finalize-type
                • Closure
                • Register-type
                • Finalizer
                • Value-type
                • Record-type
                • Command
                • Plaintext-type
                • Finalization-option
                • Visibility
                • Register
                • Reference
                • Programid
                • Locator
                • Finalization
                • Entry-type
                • Regaccess
                • Program
                • Interface-type
                • Ident+ptype
                • Ident+etype
                • Function-output
                • Finalize-output
                • Finalize-input
                • Closure-output
                • Closure-input
                • Assert-op
                • Function-input
                • Equal-op
                • Finalize-command
                • Ternary-op
                  • Ternary-op-case
                    • Ternary-op-fix
                    • Ternary-op-equiv
                    • Ternary-opp
                    • Ternary-op-ternary
                    • Ternary-op-kind
                  • Import
                  • Ident+ptype-list
                  • Operand-list
                  • Ident+etype-list
                  • Programdef-list
                  • Instruction-list
                  • Import-list
                  • Identifier-list
                  • Function-output-list
                  • Function-input-list
                  • Finalize-output-list
                  • Finalize-input-list
                  • Command-list
                  • Closure-output-list
                  • Closure-input-list
                • Parser
                • Concrete-syntax
              • Concrete-syntax
          • Leo
        • Bigmems
        • Builtins
        • Execloader
        • Solidity
        • Paco
        • Concurrent-programs
        • Bls12-377-curves
      • Debugging
      • Community
      • Std
      • Proof-automation
      • Macro-libraries
      • ACL2
      • Interfacing-tools
      • Hardware-verification
      • Software-verification
      • Math
      • Testing-utilities
    • Ternary-op

    Ternary-op-case

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

    Short Form

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

    (ternary-op-case x :ternary)

    is essentially just a safer alternative to writing:

    (equal (ternary-op-kind x) :ternary)

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

    Long Form

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

    (ternary-op-case x
      :ternary ...)

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