[llvm-bugs] [Bug 26007] Clang-cl checks on copy-constructor on during initialization

[via llvm-bugs]

https://llvm.org/bugs/show_bug.cgi?id=26007

David Majnemer <david.majnemer at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |david.majnemer at gmail.com
         Resolution|---                         |INVALID

--- Comment #1 from David Majnemer <david.majnemer at gmail.com> ---
This is not a bug because clang's compatibility with MSVC stops at the water's
edge.  Our compatibility story is built around making clang acceptable with
Microsoft's header files (the Windows SDK, Direct X SDK, VC++ headers, etc.)
but our compatibility is less strong with user-written code because such code
can easily work with standards conforming compilers like clang and other, less
conforming, compilers.

In this case, the code can be written as:
std::atomic<bool> b(true);

Unless you can demonstrate how something like "std::atomic<bool> b = true;"
occurs in Microsoft's headers, then I am afraid this bug must be closed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20160104/1c5ff81f/attachment.html>