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: Avoid duplicate count of features #151

Merged
merged 3 commits into from
Sep 21, 2022
Merged

Conversation

brendan-ward
Copy link
Member

As noted in #149 comment, we were calculating the count of features twice, which incurs extra and unnecessary overhead. This removes that duplication.

@brendan-ward brendan-ward merged commit 1e70f63 into main Sep 21, 2022
@brendan-ward brendan-ward deleted the consolidate_count branch September 21, 2022 16:51
if max_features > feature_count:
max_features = feature_count
elif max_features > feature_count:
max_features = feature_count

return skip_features, max_features
Copy link
Member

Choose a reason for hiding this comment

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

One small comment: should we maybe rename this processed max_features (not the original keyword) to num_features, to make the actual meaning clearer?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, good idea. Coming up... (sorry, should have requested review on this)

Copy link
Member

Choose a reason for hiding this comment

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

sorry, should have requested review on this

no, it has been here for a long time, no problem to merge (it's easy to do follow-ups if needed)

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.

2 participants