You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Paul King (JIRA)" <ji...@apache.org> on 2019/05/25 09:02:00 UTC
[jira] [Closed] (GROOVY-8503) Fund Groovy Development
[ https://issues.apache.org/jira/browse/GROOVY-8503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul King closed GROOVY-8503.
-----------------------------
Resolution: Implemented
Now that we have the open collective, we can close this issue.
> Fund Groovy Development
> -----------------------
>
> Key: GROOVY-8503
> URL: https://issues.apache.org/jira/browse/GROOVY-8503
> Project: Groovy
> Issue Type: Planned Work
> Reporter: mgroovy
> Priority: Major
> Labels: Bounty, Fund, Funding, PayPal, Payment, Pledge
>
> Join the HMS Groovy Bounty, Pledge Allegiance and Pay your Groovy Pals !
> This is an experimental umbrella task to collect pledges/bounties that people commit to paying to a (to be created) Groovy funding / developer 's Paypal address on completion of a specific Groovy feature or fix.
> If you would like to pledge for a task, just add the task name and the amount as a comment below, and I will update the totals in each currency.
> Current feature bounties:
> ||Name||Issue||Amount pledged||Description||
> |Make Groovy Java 9 compatible| |100 EUR|General ongoing development efforts to make Groovy compatible with Java 9 features|
> |var & final RHS type support| |100 EUR|Support
> final x = RHS -> final typeof(RHS)
> var typeof(RHS) x = RHS
> for the most common practical cases|
> |Non-map based named parameters|GROOVY-8451|300 EUR|Support type safe, flexible named parameters for ctors and methods, in addition to the existing, restricted map-based named parameters|
> |-Global constructor call support without new keyword-|GROOVY-8490|-200 EUR-|-Extend @Newify so that calling class ctors can be easily enabled for a whole project-|
> |block type closures|(GROOVY-6880,GROOVY-8301)|200 EUR|Support a mechanism to inline "closures" that actually semantically represent block constructs, so that return/break/continue work as for a regular code block, and the unnecessary performance hit in these cases can be avoided|
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)