dilyanpalauzov commented on PR #2319: URL: https://github.com/apache/groovy/pull/2319#issuecomment-3428447615
At https://groovy-lang.org/releasenotes/groovy-4.0.html#Groovy4.0-indy-only is written: > For many versions, Groovy could generate classic call-site based bytecode or bytecode targeting the JDK7+ invoke dynamic ("indy") bytecode instructions. You could switch between them with a compiler switch and we had two sets of jars ("normal" and "-indy") built with and without the switch enabled. In Groovy 4.0, only bytecode using the latter approach can be generated. For me this means that classic-site based bytecode cannot be generated and thus indy-generation is always enabled. (from the above hyperlink) > Currently, the Groovy runtime still contains any necessary support for classes compiled using older versions of Groovy. Is https://github.com/apache/groovy/pull/1934 about removing support for interpreting files, compiled using Groovy 3 and utilizing call-site based bytecode? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
