• Top
    • Documentation
    • Books
    • Boolean-reasoning
    • Projects
    • Debugging
    • Std
    • Proof-automation
    • Macro-libraries
    • ACL2
    • Interfacing-tools
    • Hardware-verification
    • Software-verification
      • Kestrel-books
        • Crypto-hdwallet
        • Apt
        • Error-checking
        • Fty-extensions
        • Isar
        • Kestrel-utilities
        • Set
        • Soft
        • C
          • Syntax-for-tools
          • Atc
            • Atc-implementation
              • Atc-abstract-syntax
              • Atc-pretty-printer
              • Atc-event-and-code-generation
                • Atc-symbolic-computation-states
                • Atc-symbolic-execution-rules
                • Atc-gen-ext-declon-lists
                • Atc-function-and-loop-generation
                • Atc-statement-generation
                • Atc-gen-fileset
                • Atc-gen-everything
                • Atc-gen-obj-declon
                • Atc-gen-fileset-event
                • Atc-tag-tables
                • Atc-expression-generation
                • Atc-generation-contexts
                  • Atc-contextualize
                  • Atc-premise
                    • Atc-premise-fix
                    • Atc-premise-case
                      • Atc-premise-equiv
                      • Atc-premisep
                      • Atc-premise-cvalues
                      • Atc-premise-cvalue
                      • Atc-premise-compustate
                      • Atc-premise-test
                      • Atc-premise-kind
                    • Atc-contextualize-compustate
                    • Atc-context
                    • Atc-context-extend
                    • Irr-atc-context
                    • Atc-premise-list
                  • Atc-gen-wf-thm
                  • Term-checkers-atc
                  • Atc-variable-tables
                  • Term-checkers-common
                  • Atc-gen-init-fun-env-thm
                  • Atc-gen-appconds
                  • Read-write-variables
                  • Atc-gen-thm-assert-events
                  • Test*
                  • Atc-gen-prog-const
                  • Atc-gen-expr-bool
                  • Atc-theorem-generation
                  • Atc-tag-generation
                  • Atc-gen-expr-pure
                  • Atc-function-tables
                  • Atc-object-tables
                • Fty-pseudo-term-utilities
                • Atc-term-recognizers
                • Atc-input-processing
                • Atc-shallow-embedding
                • Atc-process-inputs-and-gen-everything
                • Atc-table
                • Atc-fn
                • Atc-pretty-printing-options
                • Atc-types
                • Atc-macro-definition
              • Atc-tutorial
            • Language
            • Representation
            • Transformation-tools
            • Insertion-sort
            • Pack
          • Bv
          • Imp-language
          • Event-macros
          • Java
          • Bitcoin
          • Ethereum
          • Yul
          • Zcash
          • ACL2-programming-language
          • Prime-fields
          • Json
          • Syntheto
          • File-io-light
          • Cryptography
          • Number-theory
          • Lists-light
          • Axe
          • Builtins
          • Solidity
          • Helpers
          • Htclient
          • Typed-lists-light
          • Arithmetic-light
        • X86isa
        • Axe
        • Execloader
      • Math
      • Testing-utilities
    • Atc-premise

    Atc-premise-case

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

    Short Form

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

    (atc-premise-case x :compustate)

    is essentially just a safer alternative to writing:

    (equal (atc-premise-kind x) :compustate)

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

    Long Form

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

    (atc-premise-case x
      :compustate ...
      :cvalue ...
      :cvalues ...
      :test ...)

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