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

Michael Park commented on MESOS-2663:
-------------------------------------

{noformat}
commit 2666e7b9b5509a967e66efc3e5125fde22c83224
Refs:
Author:     Michael Park <[email protected]>
AuthorDate: Sun Apr 26 12:25:42 2015 -0700
Commit:     Benjamin Hindman <[email protected]>
CommitDate: Sun Apr 26 12:25:43 2015 -0700

    Removed <stout/tuple.hpp> from stout.

    Also required switching from 'tuples::' to 'std::'.

    Review: https://reviews.apache.org/r/33567
{noformat}

{noformat}
commit 6b8d32672f3ea4da6a3f1a834af153dd85f126d0
Refs:
Author:     Michael Park <[email protected]>
AuthorDate: Sun Apr 26 12:26:10 2015 -0700
Commit:     Benjamin Hindman <[email protected]>
CommitDate: Sun Apr 26 12:26:10 2015 -0700

    Switched from 'tuples::' to 'std::' in libprocess.

    Review: https://reviews.apache.org/r/33568
{noformat}

{noformat}
commit d3dfbd9bcf41105abfab5306b309c2a772167323
Refs:
Author:     Michael Park <[email protected]>
AuthorDate: Sun Apr 26 12:26:34 2015 -0700
Commit:     Benjamin Hindman <[email protected]>
CommitDate: Sun Apr 26 12:26:35 2015 -0700

    Switched from 'tuples::' to 'std::' in Mesos.

    Review: https://reviews.apache.org/r/33569
{noformat}

> Remove <stout/tuple.hpp> and switch from tuples:: to std::
> ----------------------------------------------------------
>
>                 Key: MESOS-2663
>                 URL: https://issues.apache.org/jira/browse/MESOS-2663
>             Project: Mesos
>          Issue Type: Task
>          Components: libprocess, stout
>            Reporter: Michael Park
>            Assignee: Michael Park
>              Labels: mesosphere
>             Fix For: 0.23.0
>
>
> Once the pre-C\+\+11 codepaths are removed, {{<stout/tuple.hpp>}} becomes 
> useless. Remove it and switch the instances of {{tuples::}} to {{std::}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to