Sometimes hashes of expander instances are clashing on JRuby and TruffleRuby, making CI runs fail inconsistently. Restarting the jobs usually fixes it.
One theory is that we might have two pattern classes that differ in only one bit in their hash, and as we use binary or, there's a chance this difference will not matter. We should move to addition or xor to avoid this issue.
Sometimes hashes of expander instances are clashing on JRuby and TruffleRuby, making CI runs fail inconsistently. Restarting the jobs usually fixes it.
One theory is that we might have two pattern classes that differ in only one bit in their hash, and as we use binary or, there's a chance this difference will not matter. We should move to addition or xor to avoid this issue.