Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Subsume should succeed even when the tuple is not present in the database #478

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

yihozhang
Copy link
Collaborator

Fixes #462

@yihozhang yihozhang requested a review from a team as a code owner December 5, 2024 02:39
@yihozhang yihozhang requested review from FTRobbin and removed request for a team December 5, 2024 02:39
@@ -124,13 +124,6 @@ impl Table {
Some(&self.vals[off].1)
}

pub(crate) fn get_mut(&mut self, inputs: &[Value]) -> Option<&mut TupleOutput> {
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

get_mut() is unsafe because it does not require the caller to update the timestamp. Use insert_and_merge instead.

Copy link

codspeed-hq bot commented Dec 5, 2024

CodSpeed Performance Report

Merging #478 will not alter performance

Comparing yihozhang-fix-subsume (61fd8f3) with main (246b195)

Summary

✅ 8 untouched benchmarks

@yihozhang yihozhang marked this pull request as draft December 5, 2024 02:57
@yihozhang
Copy link
Collaborator Author

Actually this fix is bad. Will re-do it after #461 is merged since the right fix will have merge conflict with #461

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.

Subsumption confusing semantics
1 participant