Non-PMC +1, purely from a Groovy user's perspective...
On 31.12.2017 04:51, Nathan Harvey wrote:
I'm starting a vote to add the ability to declare extension methods within the same project that they are used, removing the requirement to isolate them to a separate/external dependency. More discussion here: http://www.groovy-lang.org/mailing-lists.html#nabble-f372993 One question left remaining is the syntax for declaring the extension methods. I think the best option, at least to start out with, is to use an annotation. For example: @Extension public String upper(String self) { ... } This follows existing paradigms and doesn't introduce any new syntax. The possible downside is a hit to IDE performance because it relies on annotations. In theory, once the ability to declare extensions within the project exists, this can be managed much more easily, and another vote could be had to decide the best syntax. Please vote on adding the new feature to Apache Groovy 3.0.0 and 2.6.0 releases. [ ] +1 The feature sounds good [ ] 0 I don't have a strong opinion about this, but I assume it's ok [ ] -1 Because... PS this is the first vote I've called, hopefully I did everything right. Thanks to Daniel for helping me out. -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
