You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Eric Milles (Jira)" <ji...@apache.org> on 2022/01/02 23:47:00 UTC

[jira] [Commented] (GROOVY-2456) Support in-Keyword for Strings

    [ https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17467729#comment-17467729 ] 

Eric Milles commented on GROOVY-2456:
-------------------------------------

[~paulk]
"in" is somewhat of a useless operator for strings (aka {{CharSequence}}) since it maps to "equals" not "contains".  Is there still apetite for disconnecting "in" from "isCase" for strings in Groovy 4 or later?

> Support in-Keyword for Strings
> ------------------------------
>
>                 Key: GROOVY-2456
>                 URL: https://issues.apache.org/jira/browse/GROOVY-2456
>             Project: Groovy
>          Issue Type: New Feature
>          Components: groovy-jdk
>    Affects Versions: 1.5.1
>            Reporter: Bernd Schiffer
>            Priority: Major
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that with the in-Keyword with Lists (//2), too. But you can't do this with the in-Keyword with Strings. It would be a consistent behaviour from Groovy if you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)