[
https://issues.apache.org/jira/browse/GROOVY-10891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17653470#comment-17653470
]
ASF GitHub Bot commented on GROOVY-10891:
-----------------------------------------
paulk-asert commented on PR #1839:
URL: https://github.com/apache/groovy/pull/1839#issuecomment-1368542797
We picked the name `findResult` many years ago. Naming is hard. I wasn't
going to open the naming can of worms myself. Just plugging that hole in the
existing named functions.
But on naming, I think the idea was that if you got a result (being
"non-null") that was a match whereas what was regarded as more common case of
wanting Groovy truth was find/findAll. If we hadn't already locked in the
find/findAll naming many years earlier again, we might not have chosen
findResult/findResults for the non-null case.
> We should have variants of findResult/s with no Closure which use
> Closure.IDENTITY in that case
> -----------------------------------------------------------------------------------------------
>
> Key: GROOVY-10891
> URL: https://issues.apache.org/jira/browse/GROOVY-10891
> Project: Groovy
> Issue Type: Improvement
> Components: groovy-jdk
> Reporter: Paul King
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
