[LLVMbugs] [Bug 15299] tuple constructor should be marked explicit

bugzilla-daemon at llvm.org bugzilla-daemon at llvm.org
Thu Jan 16 09:22:42 PST 2014


Howard Hinnant <hhinnant at apple.com> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #5 from Howard Hinnant <hhinnant at apple.com> ---
Closing.  "Won't fix" isn't exactly the right resolution.  I would have
preferred to mark this as "Extension".  The extension is so popular I do not
see any way to back it out at this point.  I am also unsure how to implement a
pedantic warning for the use of this extension.

Fortunately it isn't a huge porting impediment.  If upon porting you discover
that you have unknowingly taken advantage of this extension, you get a compile
time error, not a run time error.  And the C++11-conforming fix to get your
code portable is simple, and given by Gonzalo BG's 2013-02-19 comment.

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/20140116/0d5a179a/attachment.html>

More information about the llvm-bugs mailing list