[LLVMbugs] [Bug 23338] New: Should LFTS be restricted to C++14?

[bugzilla-daemon at llvm.org]

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

            Bug ID: 23338
           Summary: Should LFTS be restricted to C++14?
           Product: libc++
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: All Bugs
          Assignee: unassignedclangbugs at nondot.org
          Reporter: eric at efcs.ca
                CC: llvmbugs at cs.uiuc.edu, mclow.lists at gmail.com
    Classification: Unclassified

We need to decide on a policy for restricting the use of LFTS features. Most of
LFTS can be implemented using only C++11. I think these new features are useful
enough that there is a strong motivation to provide them whenever possible.

So should we allow users to use parts of the LFTS in C++11?

I think the rational for keeping it C++14 only is:

- N4335 references the C++14 standard as its base document
- C++11 should be "stable". Additions added to the language after C++11 not
break valid code.

Some other considerations:

- What restrictions do other standard libraries place on the use of the LFTS?
Should we try and match these restrictions?
- Should including the headers in C++98/C++11 explicitly cause compile errors?
(Similar to how libstdc++ handles C++11 only headers).

I'll write up documentation and rational for whatever we decide here.

-- 
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/20150424/d3bb4f0a/attachment.html>