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

Benjamin Bannier commented on MESOS-6895:
-----------------------------------------

Not supporting this construct seems [intentional or a documented 
limitation|https://github.com/llvm-mirror/clang/blob/2a3dc33f7eb936f76ea1e98154f459fa468b78c3/test/CXX/temp/temp.decls/temp.friend/p5.cpp#L63-L72].

> Loop uses dependent nested names for friend declaration which isn't supported 
> by recent clang
> ---------------------------------------------------------------------------------------------
>
>                 Key: MESOS-6895
>                 URL: https://issues.apache.org/jira/browse/MESOS-6895
>             Project: Mesos
>          Issue Type: Bug
>          Components: libprocess
>    Affects Versions: 1.2.0
>            Reporter: Benjamin Bannier
>            Assignee: Jan Schlicht
>              Labels: mesosphere
>
> https://reviews.apache.org/r/54358/ ({{bbb4058d60}}) introduced 
> {{ControlFlow}} for {{process::loop}}. Here a dependent nested name specifier 
> is used in a friend declaration which is not supported by recent clang.
> {code}
> In file included from 
> ../../../3rdparty/libprocess/src/tests/loop_tests.cpp:20:
> /private/tmp/mesos.master/3rdparty/libprocess/include/process/loop.hpp|214 
> col 32| warning: dependent nested name specifier 'ControlFlow<U>::' for 
> friend class declaration is not supported; turning off access control for 
> 'ControlFlow' [-Wunsupported-friend]
>   friend class ControlFlow<U>::Continue;
>                ~~~~~~~~~~~~~~~~^
> /private/tmp/mesos.master/3rdparty/libprocess/include/process/loop.hpp|216 
> col 32| warning: dependent nested name specifier 'ControlFlow<U>::' for 
> friend class declaration is not supported; turning off access control for 
> 'ControlFlow' [-Wunsupported-friend]
>   friend class ControlFlow<U>::Break;
>                ~~~~~~~~~~~~~~~~^
> {code}



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

Reply via email to