• Top
    • Documentation
    • Books
    • Boolean-reasoning
    • Projects
    • Debugging
    • Std
    • Proof-automation
    • Macro-libraries
    • ACL2
    • Interfacing-tools
    • Hardware-verification
      • Gl
      • Esim
      • Vl2014
      • Sv
      • Fgl
        • Fgl-rewrite-rules
        • Fgl-function-mode
        • Fgl-object
        • Fgl-solving
        • Fgl-handling-if-then-elses
        • Fgl-getting-bits-from-objects
        • Fgl-primitive-and-meta-rules
        • Fgl-counterexamples
        • Fgl-interpreter-overview
        • Fgl-correctness-of-binding-free-variables
        • Fgl-debugging
        • Fgl-testbenches
        • Def-fgl-boolean-constraint
        • Fgl-stack
          • Scratchobj
            • Scratchobj-fix
            • Scratchobj-case
              • Scratchobj-equiv
              • Scratchobj-p
              • Scratchobj-formals
              • Scratchobj-fnsym
              • Scratchobj-fgl-objlist
              • Scratchobj-fgl-obj
              • Scratchobj-cinstlist
              • Scratchobj-cinst
              • Scratchobj-bfrlist
              • Scratchobj-kind
              • Scratchobj-bfr
            • Minor-frame
            • Major-frame
            • Major-stack
            • Scratchlist
            • Minor-stack
          • Fgl-rewrite-tracing
          • Def-fgl-param-thm
          • Def-fgl-thm
          • Fgl-fast-alist-support
          • Fgl-array-support
          • Advanced-equivalence-checking-with-fgl
          • Fgl-fty-support
          • Fgl-internals
        • Vwsim
        • Vl
        • X86isa
        • Svl
        • Rtl
      • Software-verification
      • Math
      • Testing-utilities
    • Scratchobj

    Scratchobj-case

    Case macro for the different kinds of scratchobj structures.

    This is an ACL2::fty sum-type case macro, typically introduced by defflexsum or fty::deftagsum. It allows you to safely check the type of a scratchobj structure, or to split into cases based on its type.

    Short Form

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

    (scratchobj-case x :fgl-obj)

    is essentially just a safer alternative to writing:

    (equal (scratchobj-kind x) :fgl-obj)

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

    Long Form

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

    (scratchobj-case x
      :fgl-obj ...
      :fgl-objlist ...
      :bfr ...
      :bfrlist ...
      :cinst ...
      :cinstlist ...
      :fnsym ...
      :formals ...)

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