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: Match seed finder util .hpp and .ipp types #1214

Closed

Conversation

stephenswat
Copy link
Member

I've discovered that #1143 introduces a subtle but rather nefarious bug in the seed finder utilities: the const qualifier on one of the types was removed in the .ipp file, but not in the corresponding .hpp file. This means that any code importing the .hpp will gladly compile the code, but because a matching implementation is not present in the .ipp file, it will rely on this implementation being made available at link time. In this particular case, that never happens, and we run into rather hard to debug linking errors. This commit resolves the issue by making sure that the function signatures between the .hpp file and the .ipp file are the same.

I've discovered that acts-project#1143 introduces a subtle but rather nefarious bug
in the seed finder utilities: the const qualifier on one of the types
was removed in the .ipp file, but not in the corresponding .hpp file.
This means that any code importing the .hpp will gladly compile the
code, but because a matching implementation is not present in the .ipp
file, it will rely on this implementation being made available at link
time. In this particular case, that never happens, and we run into
rather hard to debug linking errors. This commit resolves the issue by
making sure that the function signatures between the .hpp file and the
.ipp file are the same.
@stephenswat stephenswat added this to the next milestone Mar 30, 2022
@stephenswat stephenswat added Bug Something isn't working Component - Core Affects the Core module Impact - Minor Nuissance bug and/or affects only a single module labels Mar 30, 2022
@paulgessinger
Copy link
Member

That is indeed interesting (and not good). Thanks!

@paulgessinger
Copy link
Member

Ah I'm noticing this is changed (fixed) in #1173 too.

@stephenswat @CarloVarni what do you prefer we do here?

@stephenswat
Copy link
Member Author

That would only fix the issue for Carlo's new callable-based implementation of these functions, right?

@paulgessinger
Copy link
Member

IIUC the PR also contains this fix.

@stephenswat
Copy link
Member Author

Oh so it does, let's go with Carlo's pull request then.

@paulgessinger paulgessinger modified the milestones: next, v18.0.0 Apr 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Component - Core Affects the Core module Impact - Minor Nuissance bug and/or affects only a single module
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants