[
https://issues.apache.org/jira/browse/MESOS-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14600512#comment-14600512
]
Michael Park commented on MESOS-2925:
-------------------------------------
[~pbrett] I gave it a {{ShipIt}} on the review but how about we use the inline
member initializer syntax instead?
{code}
class Obj
{
public:
std::atomic_flag lock = ATOMIC_FLAG_INIT;
};
{code}
> Invalid usage of ATOMIC_FLAG_INIT in member initialization
> ----------------------------------------------------------
>
> Key: MESOS-2925
> URL: https://issues.apache.org/jira/browse/MESOS-2925
> Project: Mesos
> Issue Type: Bug
> Components: libprocess
> Affects Versions: 0.23.0
> Reporter: Paul Brett
>
> The C++ specification states:
> The macro ATOMIC_FLAG_INIT shall be defined in such a way that it can be used
> to initialize an object of type atomic_flag to the clear state. The macro can
> be used in the form: "atomic_flag guard = ATOMIC_FLAG_INIT; "It is
> unspecified whether the macro can be used in other initialization contexts."
> Clang catches this (although reports it erroneously as a braced scaled init
> issue) and refuses to compile libprocess.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
