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
Better process effects #11560
Better process effects #11560
Conversation
🦋 Changeset detectedLatest commit: 58145ae The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
// We might be dealing with many effects here, far more than can be spread into | ||
// an array push call (callstack overflow). So let's deal with each effect in a loop. | ||
for (var i = 0; i < effects.length; i++) { | ||
if ((filter_flags & EFFECT) !== 0) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is the if condition inside the for loop? It looks like it isn't dependent on the content so can be switched
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you mean? Feel free to put up a PR to show what you mean. :)
Fixes #11532.