[
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)
