Crucible/LLVM: Group argument equality assertions in override matching #522
Labels
subsystem: crucible-llvm
Issues related to LLVM bitcode verification with crucible-llvm
topics: error-messages
Issues involving the messages SAW produces on error
type: enhancement
Issues describing an improvement to an existing feature or capability
Crucible/LLVM currently matches arguments for overrides by collecting a bunch of assertions (from
methodSpecHandler_prestate
):The
matchArg
function is in anOverrideState
state monad, and so doesn't return the assertions it makes. We're losing granularity here: when the call tomatchArg
is made, we know that the added assertions are related to an equality condition for the override's arguments, but after the call we have no understanding of where they came from.If we keep track of which argument equality these assertions come from, we can later report that more meaningfully/at a higher level to the user.
The text was updated successfully, but these errors were encountered: