[
https://issues.apache.org/jira/browse/GROOVY-8543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438802#comment-16438802
]
Jochen Theodorou commented on GROOVY-8543:
------------------------------------------
why does the current static compiler not use Java compilation(method selection,
type flowing, etc.) at the beginning? The generics problem surely was
underestimated, but if you think about it... the static compiler started by
compiling more and more Groovy constructs static, with the goal to have the
semantics as near to the dynamic mode as it makes sense and if technically
feasible. Why should you then first let it compile to semantics that are
neither the targeted static compilation mode, nor the original dynamic mode and
not declare it as a bug on top of it?
> Support setting compileStatic by default via system properties
> --------------------------------------------------------------
>
> Key: GROOVY-8543
> URL: https://issues.apache.org/jira/browse/GROOVY-8543
> Project: Groovy
> Issue Type: New Feature
> Reporter: Daniel Sun
> Assignee: Daniel Sun
> Priority: Major
> Fix For: 3.0.0-alpha-2, 2.6.0-alpha-4
>
>
> Enable compile static by default via `-Dgroovy.compile.static=true`
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
