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

Fix overflow when adding delta #144

Merged
merged 2 commits into from
Nov 9, 2024
Merged

Fix overflow when adding delta #144

merged 2 commits into from
Nov 9, 2024

Conversation

LaurenzV
Copy link
Collaborator

@LaurenzV LaurenzV commented Nov 9, 2024

Same as #143, but with a minimal test case.

@alerque
Copy link
Member

alerque commented Nov 9, 2024

I'm new to helping out with this project and the general flow of things, but as a general rule of thumb from other projects I find it helpful to have fixes and tests in separate commits. Would you mind if I merge Simon's fix first then this on top of it as test commit? I can handle the rebasing, just asking if that general handling of code changes vs. testing is alright by you.

@khaledhosny
Copy link
Contributor

In HarfBuzz we pretty much always have tests added in the same commit that fixes them/implments the feature they test.

@LaurenzV
Copy link
Collaborator Author

LaurenzV commented Nov 9, 2024

Both are fine to me, your choice! :)

@alerque
Copy link
Member

alerque commented Nov 9, 2024

In HarfBuzz we pretty much always have tests added in the same commit that fixes them/implments the feature they test.

Sure, many projects do this and there isn't a hard and fast rule about the right way to do it.

Personally I like the workflow where one can easily git revert <commit id of fix commit> and quickly prove that the test case actually catches the bug it was intended to. With the fix and the test in the same commit one has to manually work out from reviewing the patch something to twiddle to verify the test works. Probably not relevant to this issue, but having the tests available to cherry pick also makes it easier to play around with potential alternative fixes.

@alerque alerque merged commit 7386be4 into main Nov 9, 2024
4 checks passed
@alerque alerque deleted the assertion-fix branch November 9, 2024 11:59
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