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

Jochen Theodorou edited comment on GROOVY-11158 at 8/17/23 2:42 PM:
--------------------------------------------------------------------

After looking more closely I think there is actually quite a few places that 
would require adaption, including breaking changes.


was (Author: blackdrag):
After looking more closely I tihnk there is actually quite a few places that 
would require adaption, including breaking changes.

> Explore whether we should deprecate/delete any generated callsite caching 
> related classes
> -----------------------------------------------------------------------------------------
>
>                 Key: GROOVY-11158
>                 URL: https://issues.apache.org/jira/browse/GROOVY-11158
>             Project: Groovy
>          Issue Type: Task
>            Reporter: Paul King
>            Priority: Major
>             Fix For: 5.x
>
>
> See the mailing list discussion:
> https://lists.apache.org/thread/hvfxv7j9bnrj6l48c1hnd7px4qhdn7b7
> We want to retain any classes needed for backwards compatibility, e.g. 
> classes embedded in the bytecode generated from older groovy versions. But we 
> should deprecate classes as appropriate. Some may be possible to delete 
> altogether.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to