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.

Sign up for GitHub

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

Jump to bottom

Performance: using findFirst() when possible at BetterNodeFinder #3505

Merged
merged 5 commits into from
Mar 22, 2023
Merged

Performance: using findFirst() when possible at BetterNodeFinder #3505

merged 5 commits into from
Mar 22, 2023
+5 −11

Conversation

samsonasik
Copy link
Member

No description provided.

@samsonasik
Performance: using findFirst() when possible at BetterNodeFinder

Partially verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
We cannot verify signatures from co-authors, and some of the co-authors attributed to this commit require their commits to be signed.
9917069
@samsonasik
Copy link
Member Author

All checks have passed 🎉 @TomasVotruba I think it is ready.

@samsonasik
Copy link
Member Author

@TomasVotruba I am merging it ;)

@samsonasik samsonasik merged commit b8a0d66 into main Mar 22, 2023
@samsonasik samsonasik deleted the samsonasik-patch-1 branch March 22, 2023 20:10
samsonasik added a commit that referenced this pull request May 8, 2023
@samsonasik
Performance: using findFirst() when possible at BetterNodeFinder (#3505)
3200c55 
* Performance: using findFirst() when possible at BetterNodeFinder

* add missing )

* cs fix

* cs fix

* cs fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@TomasVotruba TomasVotruba

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@samsonasik