Hi Cédric > We always said we wouldn't fall into the same trap as C++ or Scala, but > instead allow overriding existing operators. Could you please expain the trap in details? Thanks in advance :)
BTW, I adjusted the priority of custom operators to avoid parentheses in most cases. https://github.com/danielsun1106/groovy-parser/blob/customOperator/src/test/resources/core/CustomOperator_01x.groovy Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/Custom-operator-for-Groovy-3-tp5736388p5736393.html Sent from the Groovy Dev mailing list archive at Nabble.com.
