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

Use sets for widening thresholds instead of lists #1654

Merged
merged 5 commits into from
Jan 15, 2025
Merged

Use sets for widening thresholds instead of lists #1654

merged 5 commits into from
Jan 15, 2025

Conversation

karoliineh
Copy link
Member

Solves #1591

@karoliineh karoliineh added cleanup Refactoring, clean-up performance Analysis time, memory usage labels Jan 10, 2025
@karoliineh karoliineh requested a review from sim642 January 10, 2025 15:52
@karoliineh karoliineh linked an issue Jan 10, 2025 that may be closed by this pull request
@sim642 sim642 added this to the v2.6.0 milestone Jan 13, 2025
Copy link
Member

@sim642 sim642 left a comment

Choose a reason for hiding this comment

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

I'm doing an sv-benchmarks comparison run before merging, just in case. It should exercise widening thresholds a lot more than our limited tests about it.

EDIT: Differences seem to be all noise: https://goblint.cs.ut.ee/results/246-all-pr-1654/.

@sim642 sim642 merged commit 2955c1f into master Jan 15, 2025
21 checks passed
@sim642 sim642 deleted the issue-1591 branch January 15, 2025 09:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cleanup Refactoring, clean-up performance Analysis time, memory usage
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use sets for widening thresholds instead of lists
2 participants