Fix #925: inconsistent return in df_integrals.py::double_factorize #1111
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
double_factorize
method in theDFABKpointIntegrals
class had an inconsistent return. It was type-hinted to returnNone
, but had a code path that returned a value. This early return also caused a caching issue where the method would incorrectly return a cached result even when called with a newthresh
value, preventing re-computation.This commit removes the premature return statement. This allows the
thresh
parameter to take effect as intended and makes the method's behavior consistent with its type hint.