You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Yong Tang (JIRA)" <ji...@apache.org> on 2016/02/23 01:52:18 UTC
[jira] [Assigned] (MESOS-4602) Invalid usage of ATOMIC_FLAG_INIT in
member initialization
[ https://issues.apache.org/jira/browse/MESOS-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yong Tang reassigned MESOS-4602:
--------------------------------
Assignee: Yong Tang
> Invalid usage of ATOMIC_FLAG_INIT in member initialization
> ----------------------------------------------------------
>
> Key: MESOS-4602
> URL: https://issues.apache.org/jira/browse/MESOS-4602
> Project: Mesos
> Issue Type: Bug
> Components: libprocess
> Reporter: Benjamin Bannier
> Assignee: Yong Tang
> Labels: newbie, tech-debt
>
> MESOS-2925 fixed a few instances where {{ATOMIC_FLAG_INIT}} was used in initializer lists, but missed to fix {{3rdparty/libprocess/src/libevent_ssl_socket.cpp}} (even though the corresponding header was touched).
> There, {{LibeventSSLSocketImpl}}'s {{lock}} member is still (incorrectly) initialized in initializer lists, even though the member is already initialized in the class declaration, so it appears they should be dropped.
> Clang from trunk incorrectly diagnoses the initializations in the initializer lists as benign redundant braces in initialization of a scalar, but they should be fixed for the reasons stated in MESOS-2925.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)