I guess it boils down to whether the semantics/intention of getAs is different from asType or not (no Groovy magic expected ?...) -------- Ursprüngliche Nachricht --------Von: adithyank <[email protected]> Datum: 16.05.18 12:52 (GMT+01:00) An: [email protected] Betreff: Re: Java object conversion using ConfigSlurper Hi Mario Garcia,
Groovy already has Map coercion feature with which the methods of any class can be delegated to the closures in Map. This uses `as` keyword. If we implement `asType(Class)` in `ConfigObject` (ConfigObject already implements Map), some of the functionalities of existing coercion may be affected. I am not sure ! If we implement 'getAs(Class)`, existing coercion will be unaffected. So, I will prefer `getAs(Class)` first. Note : Any ways, while testing, I will test these behaviors... Pls advice -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
