• 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
        • Bv
        • Imp-language
        • Event-macros
        • Java
        • Bitcoin
        • Ethereum
        • Yul
        • Zcash
        • ACL2-programming-language
          • Primitive-functions
          • Translated-terms
          • Values
          • Evaluation
          • Program-equivalence
          • Functions
          • Packages
          • Programs
          • Interpreter
          • Evaluation-states
            • Eval-state
              • Eval-state-fix
              • Eval-state-case
                • Eval-state-p
                • Eval-state-equiv
                • Eval-state-init
                • Eval-state-trans
                • Eval-state-final
                • Eval-state-kind
                • Eval-state-error
              • Frame
              • Binding
              • Stack
          • 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
    • Eval-state

    Eval-state-case

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

    Short Form

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

    (eval-state-case x :init)

    is essentially just a safer alternative to writing:

    (equal (eval-state-kind x) :init)

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

    Long Form

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

    (eval-state-case x
      :init ...
      :trans ...
      :final ...
      :error ...)

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