• 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
          • Language
            • Abstract-syntax
            • Integer-ranges
            • Implementation-environments
            • Dynamic-semantics
            • Static-semantics
            • Grammar
            • Integer-formats
            • Types
            • Portable-ascii-identifiers
            • Values
              • Pointer
              • Member-types-of-member-values
              • Member-value-list->value-list
              • Member-value-list->name-list
              • Expr-value
              • Type-list-of-value-list
              • Type-of-value
              • Value-option
              • Init-value
                • Init-value-case
                  • Init-value-fix
                  • Init-value-equiv
                  • Init-valuep
                  • Init-value-single
                  • Init-value-list
                  • Init-value-kind
                • Value-result
                • Type-of-value-option
                • Value-list-result
                • Member-value-list-result
                • Init-value-result
                • Expr-value-result
                • Value-option-result
                • Signed/unsigned-byte-p-of-integer-values
                • Member-type-of-member-value
                • Bounds-of-integer-values
                • Value-promoted-arithmeticp
                • Init-type-of-init-value
                • Value-unsigned-integerp
                • Value-signed-integerp
                • Value-integerp
                • Value-arithmeticp
                • Value-scalarp
                • Value-realp
                • Values/membervalues
              • Integer-operations
              • Computation-states
              • Object-designators
              • Operations
              • Errors
              • Tag-environments
              • Function-environments
              • Character-sets
              • Flexible-array-member-removal
              • Arithmetic-operations
              • Pointer-operations
              • Bytes
              • Keywords
              • Real-operations
              • Array-operations
              • Scalar-operations
              • Structure-operations
            • 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
    • Init-value

    Init-value-case

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

    Short Form

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

    (init-value-case x :single)

    is essentially just a safer alternative to writing:

    (equal (init-value-kind x) :single)

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

    Long Form

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

    (init-value-case x
      :single ...
      :list ...)

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