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

Revert "Fix Performance/ExcessiveAllocations to exclude each call… #428

Merged
merged 1 commit into from
Nov 18, 2023

Conversation

Sija
Copy link
Member

@Sija Sija commented Nov 17, 2023

…s without a block"

This reverts commit 29e29b8.


This change turned out to be incorrect.

@Sija Sija added the bug label Nov 17, 2023
@Sija Sija added this to the 1.6.0 milestone Nov 17, 2023
@Sija Sija requested a review from veelenga November 17, 2023 18:49
@Sija Sija self-assigned this Nov 17, 2023
@Sija Sija enabled auto-merge November 17, 2023 18:53
@Sija Sija added the rule label Nov 17, 2023
Copy link
Member

@veelenga veelenga left a comment

Choose a reason for hiding this comment

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

Could you please help me understand the problem to be solved and why this is reverted?

@Sija
Copy link
Member Author

Sija commented Nov 18, 2023

Sure, the commit in question restricted the rule to report only calls with blocks, which is incorrect, since the same optimization can be applied to iterators (same calls without a block)

@Sija Sija requested a review from veelenga November 18, 2023 08:43
@Sija Sija merged commit 9f9d5fa into master Nov 18, 2023
@Sija Sija deleted the revert-incorrect-excessive-allocations-condition branch November 18, 2023 08:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants