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 2020/07/20 05:48:00 UTC

[jira] [Commented] (GROOVY-9638) Make GPars Part of Groovy

    [ https://issues.apache.org/jira/browse/GROOVY-9638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160913#comment-17160913 ] 

Paul King commented on GROOVY-9638:
-----------------------------------

We are unlikely to take GPars in its current form into the Groovy project. While it hasn't been very active lately, most parts of GPars still work fine with current versions of Groovy. Let us know if you spot any problems.

Having said that, now that we have streams, and Loom/fibers/continuations in the wings, large parts of GPars could be re-written. If that can't be done in the GPars project, we'd probably do it as a Groovy module. 

> Make GPars Part of Groovy
> -------------------------
>
>                 Key: GROOVY-9638
>                 URL: https://issues.apache.org/jira/browse/GROOVY-9638
>             Project: Groovy
>          Issue Type: Improvement
>            Reporter: Suminda Dharmasena
>            Priority: Major
>
> GPars had many primitives which were useful for Groovy programming not readily available in other languages.
> Since GPars is not active any more can GPars be added to the Groovy distribution and maintained. Certain features which depend on external libraries, like CSP, can be changed and where it uses external dependencies these can be replaced with internal implementations.
>  
> Maybe the project can be part of the standard library or even a subproject.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)