Skip to content

Fix meet_into keeping its own focus value when the meet is the source's - #179

Merged
luketpeterson merged 2 commits into
Adam-Vandervorst:masterfrom
imlvts:fix/meet-into-focus-value
Nov 5, 2026
Merged

luketpeterson merged 2 commits into
Adam-Vandervorst:masterfrom
imlvts:fix/meet-into-focus-value

Conversation

@imlvts

@imlvts imlvts commented Nov 3, 2026

Copy link
Copy Markdown
Collaborator

meet_into took any Identity from pmeet to mean its own value was the result. Identity(COUNTER_IDENT) means the source's value is, so a destination holding {1,2} met with a source holding {2} kept {1,2}. Integer values never return COUNTER_IDENT, which is why only the algebraic fuzzer's bitmask value type showed it.

meet_into took any Identity from pmeet to mean its own value was the
result.  Identity(COUNTER_IDENT) means the source's value is, so a
destination holding {1,2} met with a source holding {2} kept {1,2}.
Integer values never return COUNTER_IDENT, which is why only the
algebraic fuzzer's bitmask value type showed it.
@Adam-Vandervorst

Copy link
Copy Markdown
Owner

Are we sure this is the only place this occurs?

@imlvts

imlvts commented Nov 4, 2026

Copy link
Copy Markdown
Collaborator Author

bots say this is the only place, and seeing the fuzzing results and the tests, I think so as well

@luketpeterson

Copy link
Copy Markdown
Collaborator

Good fix. I was must have been thinking value meet would always be commutative when I wrote the buggy code.

Merging.

@luketpeterson
luketpeterson merged commit 8172d18 into Adam-Vandervorst:master Nov 5, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants