Return-Path: 
 <issues-return-13115-apmail-mesos-issues-archive=mesos.apache.org@mesos.apache.org>
X-Original-To: apmail-mesos-issues-archive@minotaur.apache.org
Delivered-To: apmail-mesos-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id CAE0E18ECD
	for <apmail-mesos-issues-archive@minotaur.apache.org>;
 Thu,  6 Aug 2015 12:42:04 +0000 (UTC)
Received: (qmail 45748 invoked by uid 500); 6 Aug 2015 12:42:04 -0000
Delivered-To: apmail-mesos-issues-archive@mesos.apache.org
Received: (qmail 45713 invoked by uid 500); 6 Aug 2015 12:42:04 -0000
Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@mesos.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@mesos.apache.org>
List-Post: <mailto:issues@mesos.apache.org>
List-Id: <issues.mesos.apache.org>
Reply-To: dev@mesos.apache.org
Delivered-To: mailing list issues@mesos.apache.org
Received: (qmail 45651 invoked by uid 99); 6 Aug 2015 12:42:04 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Aug 2015 12:42:04 +0000
Date: Thu, 6 Aug 2015 12:42:04 +0000 (UTC)
From: "Alexander Rojas (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12831562.1432168312000.388640.1438864924651@Atlassian.JIRA>
In-Reply-To: <JIRA.12831562.1432168312000@Atlassian.JIRA>
References: <JIRA.12831562.1432168312000@Atlassian.JIRA>
 <JIRA.12831562.1432168312437@arcas>
Subject: [jira] [Comment Edited] (MESOS-2757) Add -> operator for Option<T>,
 Try<T>, Result<T>, Future<T>.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Alexander Rojas edited comment on MESOS-2757 at 8/6/15 12:41 PM:
-----------------------------------------------------------------

Can you guys explain the rationale behind this? I feel adding this operator gives the sense that the underlying type is a pointer while it is actually not.

Personally I think it settles a bad precedent on how to use operator overload. However, if we still see value on this, then for the sake of completion, at least the dereferencing operator should be overloaded as well.


was (Author: arojas):
Can you guys explain the rationale behind this? I feel adding this operator gives the sense that the underlying type is a pointer while it is actually not.

Personally I think it settles a bad precedent on how to use operator overload.

> Add -> operator for Option<T>, Try<T>, Result<T>, Future<T>.
> ------------------------------------------------------------
>
>                 Key: MESOS-2757
>                 URL: https://issues.apache.org/jira/browse/MESOS-2757
>             Project: Mesos
>          Issue Type: Improvement
>          Components: libprocess, stout
>            Reporter: Joris Van Remoortere
>            Assignee: Benjamin Mahler
>              Labels: c++11, option, stout, twitter
>
> Let's add operator overloads to Option<T> to allow access to the underlying T using the `->` operator.



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