[
https://issues.apache.org/jira/browse/GROOVY-9904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17270153#comment-17270153
]
Romain Bioteau commented on GROOVY-9904:
----------------------------------------
Ok, thanks for the insights, I understand that this use case should not be that
common in groovy code and will add a migration warning about prefering
extension methods in those cases (I'm migrating from 2.4.x where those methods
are not deprecated, as 2.4.x is still maintained it could worth it to add the
deprecation flags in those versions to ease the migration)
Thanks for your help
> DefaultGroovyMethods.size() breaking change in 3.0.x
> ----------------------------------------------------
>
> Key: GROOVY-9904
> URL: https://issues.apache.org/jira/browse/GROOVY-9904
> Project: Groovy
> Issue Type: Bug
> Components: groovy-runtime
> Affects Versions: 3.0.7
> Reporter: Romain Bioteau
> Priority: Major
>
> {code:java}
> org.codehaus.groovy.runtime.DefaultGroovyMethods.size(StringBuffer sb) {code}
> doesn't have the same behavior between 2.5.x and 3.0.x
> {code:java}
> assert org.codehaus.groovy.runtime.DefaultGroovyMethods.size(new
> StringBuffer('test')) == 4 // true in 2.5.x
> assert org.codehaus.groovy.runtime.DefaultGroovyMethods.size(new
> StringBuffer('test')) == 4 // false in 3.0.x, expected 1{code}
> I didn't find any explanation about this change in the release note.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
