Handling for OperandTypes.sequence changed in 33f4ab40bbee26e06209061c35a422f2f1e05371 such that iFormalOperand passed to subcheckers is no longer always zero, but is instead:
- Zero if the subchecker is FamilyOperandTypeChecker.
- Otherwise, the operand number in the overall sequence.
It causes problems for the way we're using sequence checkers in Druid, since we don't always use FamilyOperandTypeChecker, but we do assume the old behavior: that iFormalOperand is always zero, and therefore we can put any checker into the sequence without it being "aware" that it is in a sequence.
I marked this as a bug in case this change was made accidentally. If it was made for a reason, please let me know. Thanks.