Thanks, Nadim, for the quick fix.
I can confirm that this solves that crash in analyzing my model.
However, my full model still causes Verifpal to crash. I've been trying to minimize the test case, and I can't eliminate much of the model without also eliminating the crash. I plan to release this model publicly, but I haven't yet asked the internal open-source office here at Google for permission to do that. So, I don't think I can send you the full model file to debug on your side.
I'm going to keep trying to minimize the model and debug the crash, but I'm not sure how much more time I can put into it. If you have any suggestions that would help narrow down the model line it came from, that might help me produce a minimized test case.
The traceback I get is from nearly exactly the same place in the code.
panic: runtime error: index out of range  with length 2
goroutine 1243 [running]:verifpal.com/cmd/vplogic.valuePerformPrimitiveRewrite(0xc00022b1b5
, 0x5, 0xc002272140, 0x1, 0x1, 0x2, 0x0, 0xffffffffffffffff, 0xc000021580, 0x3, ...) verifpal.com/cmd/vplogic/value.go:246
, 0x2, 0x2, 0x48, 0xc000021580, 0x3, 0xc000d22a00, 0x59, 0x59, 0xc002418000, ...) verifpal.com/cmd/vplogic/value.go:321
, 0x3, 0xc000d22a00, 0x59, 0x59, 0xc002418000, 0x59, 0x59, 0xc000b60900, 0x59, ...) verifpal.com/cmd/vplogic/value.go:378
, 0x3, 0xc000d22a00, 0x59, 0x59, 0xc002418000, 0x59, 0x59, 0xc000b60900, 0x59, ...) verifpal.com/cmd/vplogic/verifyactive.go:164
, 0x3, 0x4, 0xc000332000, 0x59, 0x92, 0xc000320000, 0x59, 0x8f, 0xc0001a3800, ...) verifpal.com/cmd/vplogic/verifyactive.go:86
, 0xc00231c780, 0x1, 0x0, 0xc000205500, 0x52, 0x8f, 0xc000e1e000, 0x52, 0x80, ...) verifpal.com/cmd/vplogic/verifyactive.go:109
created by verifpal.com/cmd/vplogic.verifyActiveScan verifpal.com/cmd/vplogic/verifyactive.go:108
Can you add some unit tests or use the "testing/quick" package (QuickCheck for Go) to test this part of the code?