[
https://issues.apache.org/jira/browse/GROOVY-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15505900#comment-15505900
]
Abel Salgado Romero commented on GROOVY-1724:
---------------------------------------------
Thanks, I can use that in some points, but not all.
I guess from the answer that abstract class coercion comes with those caveats.
Just to clarify what I was trying to achieve, I though it could be nice to use
a closure to settup Guice Modules since they require to write a single method
(https://github.com/google/guice/wiki/Motivation#dependency-injection-with-guice).
Nothing more to add.
> Extend Map coercion to classes
> ------------------------------
>
> Key: GROOVY-1724
> URL: https://issues.apache.org/jira/browse/GROOVY-1724
> Project: Groovy
> Issue Type: Improvement
> Reporter: Guillaume Delcroix
> Assignee: Jochen Theodorou
> Fix For: 1.1-beta-3
>
>
> Currently, it is possible to define Map coercion to interfaces:
> [foo: {}, bar: {}] as SomeInterface
> The mechanism leverages Java proxies and invocation handlers.
> The mechanism should be enhanced to allow extending classes as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
