On 28.08.2018 19:45, mg wrote:
Since I just stumbled across this behavior while helping a junior developer debug his code: Why does statically compiled Groovy (2.5.2) return null from void methods, instead of raising a compile error ?
i was actually not aware we kept this logic for static compilation, but essentially it is like that because of dynamic Groovy, which derives this from the reflective and methodhandles based method invocation
bye Jochen
