[ https://issues.apache.org/jira/browse/GROOVY-2456 ]
Paul King deleted comment on GROOVY-2456:
-----------------------------------
was (Author: JIRAUSER300949):
This message was created automatically by email delivery software.
Could not deliver an email to at least one recipient.
Message sent on 6/20/2023 12:20:01 AM
Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings
Message-Id: <jira.12814015.1198934585000.83614.1687213200...@atlassian.jira>
Sender: j...@apache.org
The affected recipients are:
bernd.schif...@akquinet.de - 550 5.4.1 Recipient address rejected: Access
denied. AS(201806281) [AM0EUR02FT007.eop-EUR02.prod.protection.outlook.com
2023-06-19T22:20:09.466Z 08DB70F18352CE78]
> 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: Paul King
> Priority: Major
> Labels: breaking, breaking_change
> Attachments: deliveryreport.txt
>
>
> 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.10#820010)
