[cfe-dev] [RFC] C++17 Parallel STL ∥ a new project

[JF Bastien via cfe-dev]

> On Aug 22, 2018, at 11:06 AM, Chris Lattner <clattner at nondot.org> wrote:
> 
> On Aug 21, 2018, at 2:13 PM, JF Bastien via cfe-dev <cfe-dev at lists.llvm.org <mailto:cfe-dev at lists.llvm.org>> wrote:
>> What we’re suggesting
>> 
>> Create a new repository, under the LLVM Foundation, to host Parallel STL work. This includes an implementation which can support multiple backends, correctness tests, and performance tests.
>> This repository will be importable into libc++ <https://libcxx.llvm.org/> and libstdc++ <https://gcc.gnu.org/onlinedocs/libstdc++/>. Details will be worked out later as this will be experimental for a while.
>> Contributions occur as usual, under LLVM’s contribution policy <https://llvm.org/docs/Contributing.html> (specifically, the revised <http://llvm.org/foundation/relicensing/devpolicy.patch> policy <http://llvm.org/foundation/relicensing/devpolicy.patch>).
>> New mailing lists will be created for the project (pstl-dev@ and pstl-commits@), as well as new bugzilla components, and associated Phabricator setup.
> 
> One specific question I’d like to see considered: we’re talking about splitting libc++ off to its own mailing list now.  Does it make sense for pstl to share that list, or should we add two new lists?
> 
> Besides the seeming alignment between the two projects, this would encourage collaboration across the code bases and would reduce spam moderation burden.

Tom and Mikhail might know better: they likely only want emails from pstl, which is why I suggested having its own list. The new libc++ lists should be fairly low traffic, and I agree with you that it might help with some extra collaboration. I’m OK with either.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20180822/ff3b46e9/attachment.html>