From: Jonathan Wakely Date: Tue, 11 Jul 2017 11:11:33 +0000 (+0100) Subject: Improvements to the libstdc++ FAQ and manual X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=6a28a7531b6a8f759c081bbb1b851e293e410d56;p=gcc.git Improvements to the libstdc++ FAQ and manual * doc/xml/faq.xml: Update several old entries. Improve cross-references. * doc/xml/manual/intro.xml: Add anchors to each DR. * doc/html/*: Regenerate. From-SVN: r250125 --- diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index 8dc104393a7..04a1c7f7aee 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,10 @@ +2017-07-11 Jonathan Wakely + + * doc/xml/faq.xml: Update several old entries. Improve + cross-references. + * doc/xml/manual/intro.xml: Add anchors to each DR. + * doc/html/*: Regenerate. + 2017-07-10 Jonathan Wakely * testsuite/abi/pr42230.cc: Add header for std::free. diff --git a/libstdc++-v3/doc/html/faq.html b/libstdc++-v3/doc/html/faq.html index 95386554471..34a9b2bce60 100644 --- a/libstdc++-v3/doc/html/faq.html +++ b/libstdc++-v3/doc/html/faq.html @@ -76,7 +76,8 @@
6.9. Aw, that's easy to fix!
7.1. - string::iterator is not char*; vector<T>::iterator is not T* + string::iterator is not char*; + vector<T>::iterator is not T*
7.2. What's next after libstdc++?
7.3. @@ -133,10 +134,10 @@ portability that are the hallmarks of an open-source project are applied to libstdc++.

- All of the standard classes and functions from C++98/C++03 + All of the standard classes and functions from C++98/C++03, C++11 and C++14 (such as string, vector<>, iostreams, algorithms etc.) - are freely available and atempt to be fully compliant. + are freely available and attempt to be fully compliant. Work is ongoing to complete support for the current revision of the ISO C++ Standard.

1.3.

@@ -431,7 +432,7 @@ C++ compiler.

4.2.

No 'long long' type on Solaris? -

+

Note

This answer is old and probably no longer be relevant.

By default we try to support the C99 long long type. This requires that certain functions from your C library be present.

@@ -509,7 +510,7 @@ more recent the C library. (This is also documented in the main GCC installation instructions.)

4.8.

- Can't use wchar_t/wstring on FreeBSD + Can't use wchar_t/wstring on FreeBSD

Note

This answer is old and probably no longer be relevant.

Older versions of FreeBSD's C library do not have sufficient support for wide character functions, and as a result the @@ -552,7 +553,8 @@ place), a public list of the library defects is occasionally published on the WG21 website. - Many of these issues have resulted in code changes in libstdc++. + Many of these issues have resulted in + code changes in libstdc++.

If you think you've discovered a new bug that is not listed, please post a message describing your problem to the author of @@ -570,8 +572,8 @@ these lists with terms describing your issue.

Before reporting a bug, please examine the - bugs database with the - category set to “g++”. + bugs database, with the + component set to “c++”.

6.1. Reopening a stream fails
6.2. @@ -594,8 +596,9 @@ Aw, that's easy to fix!

6.1.

Reopening a stream fails -

- One of the most-reported non-bug reports. Executing a sequence like: +

Note

This answer is old and probably no longer be relevant.

+ Prior to GCC 4.0 this was one of the most-reported non-bug reports. + Executing a sequence like this would fail: 

     #include <fstream>
     ...
@@ -606,19 +609,20 @@
     fs.close();
     fs.open("a_new_file");

- All operations on the re-opened fs will fail, or at - least act very strangely. Yes, they often will, especially if - fs reached the EOF state on the previous file. The - reason is that the state flags are not cleared - on a successful call to open(). The standard unfortunately did - not specify behavior in this case, and to everybody's great sorrow, - the proposed LWG resolution in - DR #22 is to leave the flags unchanged. You must insert a call - to fs.clear() between the calls to close() and open(), - and then everything will work like we all expect it to work. - Update: for GCC 4.0 we implemented the resolution - of DR #409 and open() - now calls clear() on success! + All operations on the re-opened fs would fail, or at + least act very strangely, especially if fs reached the + EOF state on the previous file. + The original C++98 standard did not specify behavior in this case, and + the resolution of DR #22 was to + leave the state flags unchanged on a successful call to + open(). + You had to insert a call to fs.clear() between the + calls to close() and open(), + and then everything will work as expected. + Update: For GCC 4.0 we implemented the resolution + of DR #409 and + open() + now calls clear() on success.

6.2.

-Weffc++ complains too much

@@ -626,7 +630,9 @@ libstdc++ -Weffc++-clean is not a goal of the project, for a few reasons. Mainly, that option tries to enforce object-oriented programming, while the Standard Library isn't - necessarily trying to be OO. + necessarily trying to be OO. The option also enforces outdated guidelines + from old editions of the books, and the advice isn't all relevant to + modern C++ (especially C++11 and later).

We do, however, try to have libstdc++ sources as clean as possible. If you see some simple changes that pacify -Weffc++ @@ -637,15 +643,16 @@ Another problem is the rel_ops namespace and the template comparison operator functions contained therein. If they become visible in the same namespace as other comparison functions - (e.g., “using” them and the <iterator> header), + (e.g., “using” them and the + <iterator> header), then you will suddenly be faced with huge numbers of ambiguity - errors. This was discussed on the -v3 list; Nathan Myers + errors. This was discussed on the mailing list; Nathan Myers sums things up here. The collisions with vector/string iterator types have been fixed for 3.1.

6.4.

The g++-3 headers are not ours -

+

Note

This answer is old and probably no longer be relevant.

If you are using headers in ${prefix}/include/g++-3, or if the installed library's name looks like @@ -698,11 +705,12 @@     g++ -fPIC -rdynamic -o foo ... -L. -lfoo -ldl
    

6.7.

“Memory leaks” in containers -

+

Note

This answer is old and probably no longer be relevant.

A few people have reported that the standard containers appear to leak memory when tested with memory checkers such as valgrind. - Under some configurations the library's allocators keep free memory in a + Under some (non-default) configurations the library's allocators keep + free memory in a pool for later reuse, rather than returning it to the OS. Although this memory is always reachable by the library and is never lost, memory debugging tools can report it as a leak. If you @@ -710,7 +718,7 @@ Tips for memory leak hunting first.

6.8.

- list::size() is O(n)! + list::size() is O(n)!

See the Containers @@ -734,7 +742,8 @@ creeps back in, it will be caught immediately by the testsuite - but only if such a test exists.

7.1. - string::iterator is not char*; vector<T>::iterator is not T* + string::iterator is not char*; + vector<T>::iterator is not T*
7.2. What's next after libstdc++?
7.3. @@ -749,7 +758,8 @@
7.8. How do I make std::vector<T>::capacity() == std::vector<T>::size?

7.1.

- string::iterator is not char*; vector<T>::iterator is not T* + string::iterator is not char*; + vector<T>::iterator is not T*

If you have code that depends on container<T> iterators being implemented as pointer-to-T, your code is broken. It's @@ -762,38 +772,38 @@ than a typedef for T* outweighs nearly all opposing arguments.

- Code which does assume that a vector iterator i + Code which does assume that a vector/string iterator i is a pointer can often be fixed by changing i in - certain expressions to &*i. Future revisions - of the Standard are expected to bless this usage for - vector<> (but not for basic_string<>). + certain expressions to &*i.

7.2.

What's next after libstdc++?

- Hopefully, not much. The goal of libstdc++ is to produce a - fully-compliant, fully-portable Standard Library. After that, - we're mostly done: there won't be any - more compliance work to do. -

- There is an effort underway to add significant extensions to - the standard library specification. The latest version of - this effort is described in - - The C++ Library Technical Report 1. + The goal of libstdc++ is to produce a + fully-compliant, fully-portable Standard Library. + While the C++ Standard continues to evolve the libstdc++ will + continue to track it.

7.3.

What about the STL from SGI?

- The STL from SGI, - version 3.3, was the final merge of the STL codebase. The - code in libstdc++ contains many fixes and changes, and - the SGI code is no longer under active - development. We expect that no future merges will take place. + The STL (Standard Template Library) was the inspiration for large chunks + of the C++ Standard Library, but the terms are not interchangeable and + they don't mean the same thing. The C++ Standard Library includes lots of + things that didn't come from the STL, and some of them aren't even + templates, such as std::locale and + std::thread. +

+ Libstdc++-v3 incorporates a lot of code from + the SGI STL + (the final merge was from + release 3.3). + The code in libstdc++ contains many fixes and changes compared to the + original SGI code.

In particular, string is not from SGI and makes no - use of their "rope" class (which is included as an - optional extension), nor is valarray and some others. - Classes like vector<> are, but have been - extensively modified. + use of their "rope" class (although that is included as an optional + extension), neither is valarray nor some others. + Classes like vector<> were from SGI, but have + been extensively modified.

More information on the evolution of libstdc++ can be found at the API @@ -812,13 +822,17 @@

Yes.

- The C++ Standard Library Technical Report adds many new features to - the library. The latest version of this effort is described in + The C++ Standard Library - Technical Report 1. + Technical Report 1 added many new features to the library.

- The implementation status of TR1 in libstdc++ can be tracked on the TR1 status - page. + The implementation status of TR1 in libstdc++ can be tracked + on the TR1 status page. +

+ New code should probably not use TR1, because almost everything in it has + been added to the main C++ Standard Library (usually with significant + improvements). + The TR1 implementation in libstdc++ is no longer actively maintained.

7.6.

How do I get a copy of the ISO C++ Standard?

Please refer to the Contributing @@ -878,10 +892,14 @@ the decisions, must happen before you can reasonably document a candidate C++ ABI that encompasses the standard library.

7.8.

- How do I make std::vector<T>::capacity() == std::vector<T>::size? + How do I make std::vector<T>::capacity() == std::vector<T>::size?

- The standard idiom for deallocating a vector<T>'s - unused memory is to create a temporary copy of the vector and swap their + Since C++11 just call the shrink_to_fit() member + function. +

+ Before C++11, the standard idiom for deallocating a + vector<T>'s + unused memory was to create a temporary copy of the vector and swap their contents, e.g. for vector<T> v


     std::vector<T>(v).swap(v);
diff --git a/libstdc++-v3/doc/html/manual/bugs.html b/libstdc++-v3/doc/html/manual/bugs.html index 1cdbf398dce..1ed199e432e 100644 --- a/libstdc++-v3/doc/html/manual/bugs.html +++ b/libstdc++-v3/doc/html/manual/bugs.html @@ -1,8 +1,8 @@ Bugs

Bugs
Prev Chapter 1. Status Next

Bugs

Implementation Bugs

Information on known bugs, details on efforts to fix them, and - fixed bugs are all available as part of the GCC bug tracking system, - with the category set to libstdc++. + fixed bugs are all available as part of the GCC bug tracking system, + under the component “libstdc++”.

Standard Bugs

Everybody's got issues. Even the C++ Standard Library.

@@ -12,219 +12,221 @@ a consensus on proposed solutions, we often incorporate the solution.

Here are the issues which have resulted in code changes to the library. - The links are to the specific defect reports from a partial - copy of the Issues List. You can read the full version online + The links are to the full version of the Issues List. + You can read the full version online at the ISO C++ Committee homepage.

If a DR is not listed here, we may simply not have gotten to - it yet; feel free to submit a patch. Search the include/bits - and src directories for appearances of + it yet; feel free to submit a patch. Search the + include and + src + directories for appearances of _GLIBCXX_RESOLVE_LIB_DEFECTS for examples of style. Note that we usually do not make changes to the code until an issue has reached DR status. -

5: +

5: string::compare specification questionable

This should be two overloaded functions rather than a single function. -

17: +

17: Bad bool parsing

Apparently extracting Boolean values was messed up... -

19: +

19: "Noconv" definition too vague

If codecvt::do_in returns noconv there are no changes to the values in [to, to_limit). -

22: +

22: Member open vs flags

Re-opening a file stream does not clear the state flags. -

23: +

23: Num_get overflow result

Implement the proposed resolution. -

25: +

25: String operator<< uses width() value wrong

Padding issues. -

48: +

48: Use of non-existent exception constructor

An instance of ios_base::failure is constructed instead. -

49: +

49: Underspecification of ios_base::sync_with_stdio

The return type is the previous state of synchronization. -

50: +

50: Copy constructor and assignment operator of ios_base

These members functions are declared private and are thus inaccessible. Specifying the correct semantics of "copying stream state" was deemed too complicated. -

60: +

60: What is a formatted input function?

This DR made many widespread changes to basic_istream and basic_ostream all of which have been implemented. -

63: +

63: Exception-handling policy for unformatted output

Make the policy consistent with that of formatted input, unformatted input, and formatted output. -

68: +

68: Extractors for char* should store null at end

And they do now. An editing glitch in the last item in the list of [27.6.1.2.3]/7. -

74: +

74: Garbled text for codecvt::do_max_length

The text of the standard was gibberish. Typos gone rampant. -

75: +

75: Contradiction in codecvt::length's argument types

Change the first parameter to stateT& and implement the new effects paragraph. -

83: +

83: string::npos vs. string::max_size()

Safety checks on the size of the string should test against max_size() rather than npos. -

90: +

90: Incorrect description of operator>> for strings

The effect contain isspace(c,getloc()) which must be replaced by isspace(c,is.getloc()). -

91: +

91: Description of operator>> and getline() for string<> might cause endless loop

They behave as a formatted input function and as an unformatted input function, respectively (except that getline is not required to set gcount). -

103: +

103: set::iterator is required to be modifiable, but this allows modification of keys.

For associative containers where the value type is the same as the key type, both iterator and const_iterator are constant iterators. -

109: +

109: Missing binders for non-const sequence elements

The binder1st and binder2nd didn't have an operator() taking a non-const parameter. -

110: +

110: istreambuf_iterator::equal not const

This was not a const member function. Note that the DR says to replace the function with a const one; we have instead provided an overloaded version with identical contents. -

117: +

117: basic_ostream uses nonexistent num_put member functions

num_put::put() was overloaded on the wrong types. -

118: +

118: basic_istream uses nonexistent num_get member functions

Same as 117, but for num_get::get(). -

129: +

129: Need error indication from seekp() and seekg()

These functions set failbit on error now. -

130: +

130: Return type of container::erase(iterator) differs for associative containers

Make member erase return iterator for set, multiset, map, multimap. -

136: +

136: seekp, seekg setting wrong streams?

seekp should only set the output stream, and seekg should only set the input stream. -

167: +

167: Improper use of traits_type::length()

op<< with a const char* was calculating an incorrect number of characters to write. -

169: +

169: Bad efficiency of overflow() mandated

Grow efficiently the internal array object. -

171: +

171: Strange seekpos() semantics due to joint position

Quite complex to summarize... -

181: +

181: make_pair() unintended behavior

This function used to take its arguments as reference-to-const, now it copies them (pass by value). -

195: +

195: Should basic_istream::sentry's constructor ever set eofbit?

Yes, it can, specifically if EOF is reached while skipping whitespace. -

211: +

211: operator>>(istream&, string&) doesn't set failbit

If nothing is extracted into the string, op>> now sets failbit (which can cause an exception, etc., etc.). -

214: +

214: set::find() missing const overload

Both set and multiset were missing overloaded find, lower_bound, upper_bound, and equal_range functions for const instances. -

231: +

231: Precision in iostream?

For conversion from a floating-point type, str.precision() is specified in the conversion specification. -

233: +

233: Insertion hints in associative containers

Implement N1780, first check before then check after, insert as close to hint as possible. -

235: +

235: No specification of default ctor for reverse_iterator

The declaration of reverse_iterator lists a default constructor. However, no specification is given what this constructor should do. -

241: +

241: Does unique_copy() require CopyConstructible and Assignable?

Add a helper for forward_iterator/output_iterator, fix the existing one for input_iterator/output_iterator to not rely on Assignability. -

243: +

243: get and getline when sentry reports failure

Store a null character only if the character array has a non-zero size. -

251: +

251: basic_stringbuf missing allocator_type

This nested typedef was originally not specified. -

253: +

253: valarray helper functions are almost entirely useless

Make the copy constructor and copy-assignment operator declarations public in gslice_array, indirect_array, mask_array, slice_array; provide definitions. -

265: +

265: std::pair::pair() effects overly restrictive

The default ctor would build its members from copies of temporaries; now it simply uses their respective default ctors. -

266: +

266: bad_exception::~bad_exception() missing Effects clause

The bad_* classes no longer have destructors (they are trivial), since no description of them was ever given. -

271: +

271: basic_iostream missing typedefs

The typedefs it inherits from its base classes can't be used, since (for example) basic_iostream<T>::traits_type is ambiguous. -

275: +

275: Wrong type in num_get::get() overloads

Similar to 118. -

280: +

280: Comparison of reverse_iterator to const reverse_iterator

Add global functions with two template parameters. (NB: not added for now a templated assignment operator) -

292: +

292: Effects of a.copyfmt (a)

If (this == &rhs) do nothing. -

300: +

300: List::merge() specification incomplete

If (this == &x) do nothing. -

303: +

303: Bitset input operator underspecified

Basically, compare the input character to is.widen(0) and is.widen(1). -

305: +

305: Default behavior of codecvt<wchar_t, char, mbstate_t>::length()

Do not specify what codecvt<wchar_t, char, mbstate_t>::do_length must return. -

328: +

328: Bad sprintf format modifier in money_put<>::do_put()

Change the format string to "%.0Lf". -

365: +

365: Lack of const-qualification in clause 27

Add const overloads of is_open. -

387: +

387: std::complex over-encapsulated

Add the real(T) and imag(T) members; in C++11 mode, also adjust the existing real() and imag() members and free functions. -

389: +

389: Const overload of valarray::operator[] returns by value

Change it to return a const T&. -

396: +

396: what are characters zero and one

Implement the proposed resolution. -

402: +

402: Wrong new expression in [some_]allocator::construct

Replace "new" with "::new".

408: @@ -232,39 +234,39 @@ Is vector<reverse_iterator<char*> > forbidden?

Tweak the debug-mode checks in _Safe_iterator. -

409: +

409: Closing an fstream should clear the error state

Have open clear the error flags.

431: Swapping containers with unequal allocators

Implement Option 3, as per N1599. -

432: +

432: stringbuf::overflow() makes only one write position available

Implement the resolution, beyond DR 169. -

434: +

434: bitset::to_string() hard to use

Add three overloads, taking fewer template arguments. -

438: +

438: Ambiguity in the "do the right thing" clause

Implement the resolution, basically cast less. -

445: +

445: iterator_traits::reference unspecified for some iterator categories

Change istreambuf_iterator::reference in C++11 mode. -

453: +

453: basic_stringbuf::seekoff need not always fail for an empty stream

Don't fail if the next pointer is null and newoff is zero. -

455: +

455: cerr::tie() and wcerr::tie() are overspecified

Initialize cerr tied to cout and wcerr tied to wcout. -

464: +

464: Suggestion for new member functions in standard containers

Add data() to std::vector and at(const key_type&) to std::map. -

467: +

467: char_traits::lt(), compare(), and memcmp()

Change lt. -

508: +

508: Bad parameters for ranlux64_base_01

Fix the parameters.

512: @@ -274,246 +276,246 @@ Is it undefined if a function in the standard changes in parameters?

Use &value. -

538: +

538: 241 again: Does unique_copy() require CopyConstructible and Assignable?

In case of input_iterator/output_iterator rely on Assignability of input_iterator' value_type. -

539: +

539: partial_sum and adjacent_difference should mention requirements

We were almost doing the right thing, just use std::move in adjacent_difference. -

541: +

541: shared_ptr template assignment and void

Add an auto_ptr<void> specialization. -

543: +

543: valarray slice default constructor

Follow the straightforward proposed resolution. -

550: +

550: What should the return type of pow(float,int) be?

In C++11 mode, remove the pow(float,int), etc., signatures. -

586: +

586: string inserter not a formatted function

Change it to be a formatted output function (i.e. catch exceptions). -

596: +

596: 27.8.1.3 Table 112 omits "a+" and "a+b" modes

Add the missing modes to fopen_mode. -

630: +

630: arrays of valarray

Implement the simple resolution. -

660: +

660: Missing bitwise operations

Add the missing operations. -

691: +

691: const_local_iterator cbegin, cend missing from TR1

In C++11 mode add cbegin(size_type) and cend(size_type) to the unordered containers. -

693: +

693: std::bitset::all() missing

Add it, consistently with the discussion. -

695: +

695: ctype<char>::classic_table() not accessible

Make the member functions table and classic_table public. -

696: +

696: istream::operator>>(int&) broken

Implement the straightforward resolution. -

761: +

761: unordered_map needs an at() member function

In C++11 mode, add at() and at() const. -

775: +

775: Tuple indexing should be unsigned?

Implement the int -> size_t replacements. -

776: +

776: Undescribed assign function of std::array

In C++11 mode, remove assign, add fill. -

781: +

781: std::complex should add missing C99 functions

In C++11 mode, add std::proj. -

809: +

809: std::swap should be overloaded for array types

Add the overload. -

853: +

853: to_string needs updating with zero and one

Update / add the signatures. -

865: +

865: More algorithms that throw away information

The traditional HP / SGI return type and value is blessed by the resolution of the DR. -

1339: +

1339: uninitialized_fill_n should return the end of its range

Return the end of the filled range. -

2021: +

2021: Further incorrect uses of result_of

Correctly decay types in signature of std::async. -

2049: +

2049: is_destructible underspecified

Handle non-object types. -

2056: +

2056: future_errc enums start with value 0 (invalid value for broken_promise)

Reorder enumerators. -

2059: +

2059: C++0x ambiguity problem with map::erase

Add additional overloads. -

2062: +

2062: 2062. Effect contradictions w/o no-throw guarantee of std::function swaps

Add noexcept to swap functions. -

2063: +

2063: Contradictory requirements for string move assignment

Respect propagation trait for move assignment. -

2064: +

2064: More noexcept issues in basic_string

Add noexcept to the comparison operators. -

2067: +

2067: packaged_task should have deleted copy c'tor with const parameter

Fix signatures. -

2101: +

2101: Some transformation types can produce impossible types

Use the referenceable type concept. -

2106: +

2106: move_iterator wrapping iterators returning prvalues

Change the reference type. -

2108: +

2108: No way to identify allocator types that always compare equal

Define and use is_always_equal even for C++11. -

2118: +

2118: unique_ptr for array does not support cv qualification conversion of actual argument

Adjust constraints to allow safe conversions. -

2127: +

2127: Move-construction with raw_storage_iterator

Add assignment operator taking an rvalue. -

2132: +

2132: std::function ambiguity

Constrain the constructor to only accept callable types. -

2141: +

2141: common_type trait produces reference types

Use decay for the result type. -

2144: +

2144: Missing noexcept specification in type_index

Add noexcept -

2145: +

2145: error_category default constructor

Declare a public constexpr constructor. -

2162: +

2162: allocator_traits::max_size missing noexcept

Add noexcept. -

2187: +

2187: vector<bool> is missing emplace and emplace_back member functions

Add emplace and emplace_back member functions. -

2192: +

2192: Validity and return type of std::abs(0u) is unclear

Move all declarations to a common header and remove the generic abs which accepted unsigned arguments. -

2196: +

2196: Specification of is_*[copy/move]_[constructible/assignable] unclear for non-referencable types

Use the referenceable type concept. -

2212: +

2212: tuple_size for const pair request <tuple> header

The tuple_size and tuple_element partial specializations are defined in <utility> which is included by <array>. -

2296: +

2296: std::addressof should be constexpr

Use __builtin_addressof and add constexpr to addressof for C++17 and later. -

2313: +

2313: tuple_size should always derive from integral_constant<size_t, N>

Update definitions of the partial specializations for const and volatile types. -

2328: +

2328: Rvalue stream extraction should use perfect forwarding

Use perfect forwarding for right operand. -

2329: +

2329: regex_match()/regex_search() with match_results should forbid temporary strings

Add deleted overloads for rvalue strings. -

2332: +

2332: regex_iterator/regex_token_iterator should forbid temporary regexes

Add deleted constructors. -

2399: +

2399: shared_ptr's constructor from unique_ptr should be constrained

Constrain the constructor to require convertibility. -

2400: +

2400: shared_ptr's get_deleter() should use addressof()

Use addressof. -

2401: +

2401: std::function needs more noexcept

Add noexcept to the assignment and comparisons. -

2407: +

2407: packaged_task(allocator_arg_t, const Allocator&, F&&) should neither be constrained nor explicit

Remove explicit from the constructor. -

2415: +

2415: Inconsistency between unique_ptr and shared_ptr

Create empty an shared_ptr from an empty unique_ptr. -

2418: +

2418: apply does not work with member pointers

Use mem_fn for member pointers. -

2440: +

2440: seed_seq::size() should be noexcept

Add noexcept. -

2441: +

2441: Exact-width atomic typedefs should be provided

Define the typedefs. -

2442: +

2442: call_once() shouldn't DECAY_COPY()

Remove indirection through call wrapper that made copies of arguments and forward arguments straight to std::invoke. -

2454: +

2454: Add raw_storage_iterator::base() member

Add the base() member function. -

2455: +

2455: Allocator default construction should be allowed to throw

Make noexcept specifications conditional. -

2458: +

2458: N3778 and new library deallocation signatures

Remove unused overloads. -

2459: +

2459: std::polar should require a non-negative rho

Add debug mode assertion. -

2466: +

2466: allocator_traits::max_size() default behavior is incorrect

Divide by the object type. -

2484: +

2484: rethrow_if_nested() is doubly unimplementable

Avoid using dynamic_cast when it would be ill-formed. -

2583: +

2583: There is no way to supply an allocator for basic_string(str, pos)

Add new constructor -

2684: +

2684: priority_queue lacking comparator typedef

Define the value_compare typedef. -

2770: +

2770: tuple_size<const T> specialization is not SFINAE compatible and breaks decomposition declarations

Safely detect tuple_size<T>::value and only use it if valid. -

2781: +

2781: Contradictory requirements for std::function and std::reference_wrapper

Remove special handling for reference_wrapper arguments and store them directly as the target object. -

2802: +

2802: Add noexcept to several shared_ptr related functions

Add noexcept. -

2873: +

2873: shared_ptr constructor requirements for a deleter

Use rvalues for deleters. -

2942: +

2942: LWG 2873's resolution missed weak_ptr::owner_before diff --git a/libstdc++-v3/doc/html/manual/test.html b/libstdc++-v3/doc/html/manual/test.html index 70341779ca7..f19a8e82a2c 100644 --- a/libstdc++-v3/doc/html/manual/test.html +++ b/libstdc++-v3/doc/html/manual/test.html @@ -327,13 +327,13 @@ cat 27_io/objects/char/3_xin.in | a.out
-O1 -D_GLIBCXX_ASSERTIONS you could use: -

    make RUNTESTFLAGS=--target_board=unix/-O1/-D_GLIBCXX_ASSERTIONS

+

    make check RUNTESTFLAGS=--target_board=unix/-O1/-D_GLIBCXX_ASSERTIONS

The --target_board option can also be used to run the tests multiple times in different variations. For example, to run the entire testsuite three times using -O3 but with different -std options: -

    make 'RUNTESTFLAGS=--target_board=unix/-O3\"{-std=gnu++98,-std=gnu++11,-std=gnu++14}\"'

+

    make check 'RUNTESTFLAGS=--target_board=unix/-O3\"{-std=gnu++98,-std=gnu++11,-std=gnu++14}\"'

N.B. that set of variations could also be written as unix/-O3\"{-std=gnu++98,-std=gnu++11,}\" so that the third variation would use the default for -std diff --git a/libstdc++-v3/doc/xml/faq.xml b/libstdc++-v3/doc/xml/faq.xml index 8041c1428e6..703ade5b20d 100644 --- a/libstdc++-v3/doc/xml/faq.xml +++ b/libstdc++-v3/doc/xml/faq.xml @@ -66,10 +66,10 @@ that are the hallmarks of an open-source project are applied to libstdc++. - All of the standard classes and functions from C++98/C++03 + All of the standard classes and functions from C++98/C++03, C++11 and C++14 (such as string, vector<>, iostreams, algorithms etc.) - are freely available and atempt to be fully compliant. + are freely available and attempt to be fully compliant. Work is ongoing to complete support for the current revision of the ISO C++ Standard. @@ -539,6 +539,9 @@ + + This answer is old and probably no longer be relevant. + By default we try to support the C99 long long type. This requires that certain functions from your C library be present. @@ -692,7 +695,7 @@ - Can't use wchar_t/wstring on FreeBSD + Can't use wchar_t/wstring on FreeBSD @@ -764,7 +767,8 @@ published on the WG21 website. - Many of these issues have resulted in code changes in libstdc++. + Many of these issues have resulted in + code changes in libstdc++. If you think you've discovered a new bug that is not listed, @@ -794,8 +798,8 @@ Before reporting a bug, please examine the - bugs database with the - category set to g++. + bugs database, with the + component set to c++. @@ -813,8 +817,12 @@ + + This answer is old and probably no longer be relevant. + - One of the most-reported non-bug reports. Executing a sequence like: + Prior to GCC 4.0 this was one of the most-reported non-bug reports. + Executing a sequence like this would fail: @@ -829,19 +837,20 @@ - All operations on the re-opened fs will fail, or at - least act very strangely. Yes, they often will, especially if - fs reached the EOF state on the previous file. The - reason is that the state flags are not cleared - on a successful call to open(). The standard unfortunately did - not specify behavior in this case, and to everybody's great sorrow, - the proposed LWG resolution in - DR #22 is to leave the flags unchanged. You must insert a call - to fs.clear() between the calls to close() and open(), - and then everything will work like we all expect it to work. - Update: for GCC 4.0 we implemented the resolution - of DR #409 and open() - now calls clear() on success! + All operations on the re-opened fs would fail, or at + least act very strangely, especially if fs reached the + EOF state on the previous file. + The original C++98 standard did not specify behavior in this case, and + the resolution of DR #22 was to + leave the state flags unchanged on a successful call to + open(). + You had to insert a call to fs.clear() between the + calls to close() and open(), + and then everything will work as expected. + Update: For GCC 4.0 we implemented the resolution + of DR #409 and + open() + now calls clear() on success. @@ -858,7 +867,9 @@ libstdc++ -clean is not a goal of the project, for a few reasons. Mainly, that option tries to enforce object-oriented programming, while the Standard Library isn't - necessarily trying to be OO. + necessarily trying to be OO. The option also enforces outdated guidelines + from old editions of the books, and the advice isn't all relevant to + modern C++ (especially C++11 and later). We do, however, try to have libstdc++ sources as clean as possible. If @@ -879,9 +890,10 @@ Another problem is the rel_ops namespace and the template comparison operator functions contained therein. If they become visible in the same namespace as other comparison functions - (e.g., using them and the <iterator> header), + (e.g., using them and the + <iterator> header), then you will suddenly be faced with huge numbers of ambiguity - errors. This was discussed on the -v3 list; Nathan Myers + errors. This was discussed on the mailing list; Nathan Myers sums things up here. The collisions with vector/string iterator types have been fixed for 3.1. @@ -896,6 +908,9 @@ + + This answer is old and probably no longer be relevant. + If you are using headers in ${prefix}/include/g++-3, or if @@ -981,11 +996,15 @@ + + This answer is old and probably no longer be relevant. + A few people have reported that the standard containers appear to leak memory when tested with memory checkers such as valgrind. - Under some configurations the library's allocators keep free memory in a + Under some (non-default) configurations the library's allocators keep + free memory in a pool for later reuse, rather than returning it to the OS. Although this memory is always reachable by the library and is never lost, memory debugging tools can report it as a leak. If you @@ -999,7 +1018,7 @@ - list::size() is O(n)! + list::size() is O(n)! @@ -1049,7 +1068,8 @@ - string::iterator is not char*; vector<T>::iterator is not T* + string::iterator is not char*; + vector<T>::iterator is not T* @@ -1067,11 +1087,9 @@ arguments. - Code which does assume that a vector iterator i + Code which does assume that a vector/string iterator i is a pointer can often be fixed by changing i in - certain expressions to &*i. Future revisions - of the Standard are expected to bless this usage for - vector<> (but not for basic_string<>). + certain expressions to &*i. @@ -1084,17 +1102,10 @@ - Hopefully, not much. The goal of libstdc++ is to produce a - fully-compliant, fully-portable Standard Library. After that, - we're mostly done: there won't be any - more compliance work to do. - - - There is an effort underway to add significant extensions to - the standard library specification. The latest version of - this effort is described in - - The C++ Library Technical Report 1. + The goal of libstdc++ is to produce a + fully-compliant, fully-portable Standard Library. + While the C++ Standard continues to evolve the libstdc++ will + continue to track it. @@ -1107,18 +1118,27 @@ - The STL from SGI, - version 3.3, was the final merge of the STL codebase. The - code in libstdc++ contains many fixes and changes, and - the SGI code is no longer under active - development. We expect that no future merges will take place. + The STL (Standard Template Library) was the inspiration for large chunks + of the C++ Standard Library, but the terms are not interchangeable and + they don't mean the same thing. The C++ Standard Library includes lots of + things that didn't come from the STL, and some of them aren't even + templates, such as std::locale and + std::thread. + + + Libstdc++-v3 incorporates a lot of code from + the SGI STL + (the final merge was from + release 3.3). + The code in libstdc++ contains many fixes and changes compared to the + original SGI code. In particular, string is not from SGI and makes no - use of their "rope" class (which is included as an - optional extension), nor is valarray and some others. - Classes like vector<> are, but have been - extensively modified. + use of their "rope" class (although that is included as an optional + extension), neither is valarray nor some others. + Classes like vector<> were from SGI, but have + been extensively modified. More information on the evolution of libstdc++ can be found at the @@ -1158,14 +1178,19 @@ Yes. - The C++ Standard Library Technical Report adds many new features to - the library. The latest version of this effort is described in + The C++ Standard Library - Technical Report 1. + Technical Report 1 added many new features to the library. - The implementation status of TR1 in libstdc++ can be tracked on the TR1 status - page. + The implementation status of TR1 in libstdc++ can be tracked + on the TR1 status page. + + + New code should probably not use TR1, because almost everything in it has + been added to the main C++ Standard Library (usually with significant + improvements). + The TR1 implementation in libstdc++ is no longer actively maintained. @@ -1252,13 +1277,18 @@ - How do I make std::vector<T>::capacity() == std::vector<T>::size? + How do I make std::vector<T>::capacity() == std::vector<T>::size? - The standard idiom for deallocating a vector<T>'s - unused memory is to create a temporary copy of the vector and swap their + Since C++11 just call the shrink_to_fit() member + function. + + + Before C++11, the standard idiom for deallocating a + vector<T>'s + unused memory was to create a temporary copy of the vector and swap their contents, e.g. for vector<T> v diff --git a/libstdc++-v3/doc/xml/manual/intro.xml b/libstdc++-v3/doc/xml/manual/intro.xml index 4ec74949bfb..782817e0698 100644 --- a/libstdc++-v3/doc/xml/manual/intro.xml +++ b/libstdc++-v3/doc/xml/manual/intro.xml @@ -193,8 +193,8 @@ requirements of the license of GCC. Information on known bugs, details on efforts to fix them, and - fixed bugs are all available as part of the GCC bug tracking system, - with the category set to libstdc++. + fixed bugs are all available as part of the GCC bug tracking system, + under the component libstdc++. @@ -211,71 +211,73 @@ requirements of the license of GCC. Here are the issues which have resulted in code changes to the library. - The links are to the specific defect reports from a partial - copy of the Issues List. You can read the full version online + The links are to the full version of the Issues List. + You can read the full version online at the ISO C++ Committee homepage. If a DR is not listed here, we may simply not have gotten to - it yet; feel free to submit a patch. Search the include/bits - and src directories for appearances of + it yet; feel free to submit a patch. Search the + include and + src + directories for appearances of _GLIBCXX_RESOLVE_LIB_DEFECTS for examples of style. Note that we usually do not make changes to the code until an issue has reached DR status. - 5: + 5: string::compare specification questionable This should be two overloaded functions rather than a single function. - 17: + 17: Bad bool parsing Apparently extracting Boolean values was messed up... - 19: + 19: "Noconv" definition too vague If codecvt::do_in returns noconv there are no changes to the values in [to, to_limit). - 22: + 22: Member open vs flags Re-opening a file stream does not clear the state flags. - 23: + 23: Num_get overflow result Implement the proposed resolution. - 25: + 25: String operator<< uses width() value wrong Padding issues. - 48: + 48: Use of non-existent exception constructor An instance of ios_base::failure is constructed instead. - 49: + 49: Underspecification of ios_base::sync_with_stdio The return type is the previous state of synchronization. - 50: + 50: Copy constructor and assignment operator of ios_base These members functions are declared private and are @@ -283,55 +285,55 @@ requirements of the license of GCC. "copying stream state" was deemed too complicated. - 60: + 60: What is a formatted input function? This DR made many widespread changes to basic_istream and basic_ostream all of which have been implemented. - 63: + 63: Exception-handling policy for unformatted output Make the policy consistent with that of formatted input, unformatted input, and formatted output. - 68: + 68: Extractors for char* should store null at end And they do now. An editing glitch in the last item in the list of [27.6.1.2.3]/7. - 74: + 74: Garbled text for codecvt::do_max_length The text of the standard was gibberish. Typos gone rampant. - 75: + 75: Contradiction in codecvt::length's argument types Change the first parameter to stateT& and implement the new effects paragraph. - 83: + 83: string::npos vs. string::max_size() Safety checks on the size of the string should test against max_size() rather than npos. - 90: + 90: Incorrect description of operator>> for strings The effect contain isspace(c,getloc()) which must be replaced by isspace(c,is.getloc()). - 91: + 91: Description of operator>> and getline() for string<> might cause endless loop @@ -340,7 +342,7 @@ requirements of the license of GCC. not required to set gcount). - 103: + 103: set::iterator is required to be modifiable, but this allows modification of keys. @@ -349,14 +351,14 @@ requirements of the license of GCC. are constant iterators. - 109: + 109: Missing binders for non-const sequence elements The binder1st and binder2nd didn't have an operator() taking a non-const parameter. - 110: + 110: istreambuf_iterator::equal not const This was not a const member function. Note that the DR says to @@ -364,31 +366,31 @@ requirements of the license of GCC. overloaded version with identical contents. - 117: + 117: basic_ostream uses nonexistent num_put member functions num_put::put() was overloaded on the wrong types. - 118: + 118: basic_istream uses nonexistent num_get member functions Same as 117, but for num_get::get(). - 129: + 129: Need error indication from seekp() and seekg() These functions set failbit on error now. - 130: + 130: Return type of container::erase(iterator) differs for associative containers Make member erase return iterator for set, multiset, map, multimap. - 136: + 136: seekp, seekg setting wrong streams? seekp should only set the output stream, and @@ -402,46 +404,46 @@ requirements of the license of GCC. should probably not be calling underflow(). --> - 167: + 167: Improper use of traits_type::length() op<< with a const char* was calculating an incorrect number of characters to write. - 169: + 169: Bad efficiency of overflow() mandated Grow efficiently the internal array object. - 171: + 171: Strange seekpos() semantics due to joint position Quite complex to summarize... - 181: + 181: make_pair() unintended behavior This function used to take its arguments as reference-to-const, now it copies them (pass by value). - 195: + 195: Should basic_istream::sentry's constructor ever set eofbit? Yes, it can, specifically if EOF is reached while skipping whitespace. - 211: + 211: operator>>(istream&, string&) doesn't set failbit If nothing is extracted into the string, op>> now sets failbit (which can cause an exception, etc., etc.). - 214: + 214: set::find() missing const overload Both set and multiset were missing @@ -449,47 +451,47 @@ requirements of the license of GCC. for const instances. - 231: + 231: Precision in iostream? For conversion from a floating-point type, str.precision() is specified in the conversion specification. - 233: + 233: Insertion hints in associative containers Implement N1780, first check before then check after, insert as close to hint as possible. - 235: + 235: No specification of default ctor for reverse_iterator The declaration of reverse_iterator lists a default constructor. However, no specification is given what this constructor should do. - 241: + 241: Does unique_copy() require CopyConstructible and Assignable? Add a helper for forward_iterator/output_iterator, fix the existing one for input_iterator/output_iterator to not rely on Assignability. - 243: + 243: get and getline when sentry reports failure Store a null character only if the character array has a non-zero size. - 251: + 251: basic_stringbuf missing allocator_type This nested typedef was originally not specified. - 253: + 253: valarray helper functions are almost entirely useless Make the copy constructor and copy-assignment operator declarations @@ -497,60 +499,60 @@ requirements of the license of GCC. definitions. - 265: + 265: std::pair::pair() effects overly restrictive The default ctor would build its members from copies of temporaries; now it simply uses their respective default ctors. - 266: + 266: bad_exception::~bad_exception() missing Effects clause The bad_* classes no longer have destructors (they are trivial), since no description of them was ever given. - 271: + 271: basic_iostream missing typedefs The typedefs it inherits from its base classes can't be used, since (for example) basic_iostream<T>::traits_type is ambiguous. - 275: + 275: Wrong type in num_get::get() overloads Similar to 118. - 280: + 280: Comparison of reverse_iterator to const reverse_iterator Add global functions with two template parameters. (NB: not added for now a templated assignment operator) - 292: + 292: Effects of a.copyfmt (a) If (this == &rhs) do nothing. - 300: + 300: List::merge() specification incomplete If (this == &x) do nothing. - 303: + 303: Bitset input operator underspecified Basically, compare the input character to is.widen(0) and is.widen(1). - 305: + 305: Default behavior of codecvt<wchar_t, char, mbstate_t>::length() @@ -558,20 +560,20 @@ requirements of the license of GCC. mbstate_t>::do_length must return. - 328: + 328: Bad sprintf format modifier in money_put<>::do_put() Change the format string to "%.0Lf". - 365: + 365: Lack of const-qualification in clause 27 Add const overloads of is_open. - 387: + 387: std::complex over-encapsulated Add the real(T) and imag(T) @@ -580,20 +582,20 @@ requirements of the license of GCC. free functions. - 389: + 389: Const overload of valarray::operator[] returns by value Change it to return a const T&. - 396: + 396: what are characters zero and one Implement the proposed resolution. - 402: + 402: Wrong new expression in [some_]allocator::construct Replace "new" with "::new". @@ -607,7 +609,7 @@ requirements of the license of GCC. Tweak the debug-mode checks in _Safe_iterator. - 409: + 409: Closing an fstream should clear the error state Have open clear the error flags. @@ -619,57 +621,57 @@ requirements of the license of GCC. Implement Option 3, as per N1599. - 432: + 432: stringbuf::overflow() makes only one write position available Implement the resolution, beyond DR 169. - 434: + 434: bitset::to_string() hard to use Add three overloads, taking fewer template arguments. - 438: + 438: Ambiguity in the "do the right thing" clause Implement the resolution, basically cast less. - 445: + 445: iterator_traits::reference unspecified for some iterator categories Change istreambuf_iterator::reference in C++11 mode. - 453: + 453: basic_stringbuf::seekoff need not always fail for an empty stream Don't fail if the next pointer is null and newoff is zero. - 455: + 455: cerr::tie() and wcerr::tie() are overspecified Initialize cerr tied to cout and wcerr tied to wcout. - 464: + 464: Suggestion for new member functions in standard containers Add data() to std::vector and at(const key_type&) to std::map. - 467: + 467: char_traits::lt(), compare(), and memcmp() Change lt. - 508: + 508: Bad parameters for ranlux64_base_01 Fix the parameters. @@ -688,7 +690,7 @@ requirements of the license of GCC. Use &value. - 538: + 538: 241 again: Does unique_copy() require CopyConstructible and Assignable? @@ -696,7 +698,7 @@ requirements of the license of GCC. input_iterator' value_type. - 539: + 539: partial_sum and adjacent_difference should mention requirements @@ -704,250 +706,250 @@ requirements of the license of GCC. in adjacent_difference. - 541: + 541: shared_ptr template assignment and void Add an auto_ptr<void> specialization. - 543: + 543: valarray slice default constructor Follow the straightforward proposed resolution. - 550: + 550: What should the return type of pow(float,int) be? In C++11 mode, remove the pow(float,int), etc., signatures. - 586: + 586: string inserter not a formatted function Change it to be a formatted output function (i.e. catch exceptions). - 596: + 596: 27.8.1.3 Table 112 omits "a+" and "a+b" modes Add the missing modes to fopen_mode. - 630: + 630: arrays of valarray Implement the simple resolution. - 660: + 660: Missing bitwise operations Add the missing operations. - 691: + 691: const_local_iterator cbegin, cend missing from TR1 In C++11 mode add cbegin(size_type) and cend(size_type) to the unordered containers. - 693: + 693: std::bitset::all() missing Add it, consistently with the discussion. - 695: + 695: ctype<char>::classic_table() not accessible Make the member functions table and classic_table public. - 696: + 696: istream::operator>>(int&) broken Implement the straightforward resolution. - 761: + 761: unordered_map needs an at() member function In C++11 mode, add at() and at() const. - 775: + 775: Tuple indexing should be unsigned? Implement the int -> size_t replacements. - 776: + 776: Undescribed assign function of std::array In C++11 mode, remove assign, add fill. - 781: + 781: std::complex should add missing C99 functions In C++11 mode, add std::proj. - 809: + 809: std::swap should be overloaded for array types Add the overload. - 853: + 853: to_string needs updating with zero and one Update / add the signatures. - 865: + 865: More algorithms that throw away information The traditional HP / SGI return type and value is blessed by the resolution of the DR. - 1339: + 1339: uninitialized_fill_n should return the end of its range Return the end of the filled range. - 2021: + 2021: Further incorrect uses of result_of Correctly decay types in signature of std::async. - 2049: + 2049: is_destructible underspecified Handle non-object types. - 2056: + 2056: future_errc enums start with value 0 (invalid value for broken_promise) Reorder enumerators. - 2059: + 2059: C++0x ambiguity problem with map::erase Add additional overloads. - 2062: + 2062: 2062. Effect contradictions w/o no-throw guarantee of std::function swaps Add noexcept to swap functions. - 2063: + 2063: Contradictory requirements for string move assignment Respect propagation trait for move assignment. - 2064: + 2064: More noexcept issues in basic_string Add noexcept to the comparison operators. - 2067: + 2067: packaged_task should have deleted copy c'tor with const parameter Fix signatures. - 2101: + 2101: Some transformation types can produce impossible types Use the referenceable type concept. - 2106: + 2106: move_iterator wrapping iterators returning prvalues Change the reference type. - 2108: + 2108: No way to identify allocator types that always compare equal Define and use is_always_equal even for C++11. - 2118: + 2118: unique_ptr for array does not support cv qualification conversion of actual argument Adjust constraints to allow safe conversions. - 2127: + 2127: Move-construction with raw_storage_iterator Add assignment operator taking an rvalue. - 2132: + 2132: std::function ambiguity Constrain the constructor to only accept callable types. - 2141: + 2141: common_type trait produces reference types Use decay for the result type. - 2144: + 2144: Missing noexcept specification in type_index Add noexcept - 2145: + 2145: error_category default constructor Declare a public constexpr constructor. - 2162: + 2162: allocator_traits::max_size missing noexcept Add noexcept. - 2187: + 2187: vector<bool> is missing emplace and emplace_back member functions Add emplace and emplace_back member functions. - 2192: + 2192: Validity and return type of std::abs(0u) is unclear Move all declarations to a common header and remove the generic abs which accepted unsigned arguments. - 2196: + 2196: Specification of is_*[copy/move]_[constructible/assignable] unclear for non-referencable types Use the referenceable type concept. - 2212: + 2212: tuple_size for const pair request <tuple> header The tuple_size and tuple_element @@ -955,56 +957,56 @@ requirements of the license of GCC. is included by <array>. - 2296: + 2296: std::addressof should be constexpr Use __builtin_addressof and add constexpr to addressof for C++17 and later. - 2313: + 2313: tuple_size should always derive from integral_constant<size_t, N> Update definitions of the partial specializations for const and volatile types. - 2328: + 2328: Rvalue stream extraction should use perfect forwarding Use perfect forwarding for right operand. - 2329: + 2329: regex_match()/regex_search() with match_results should forbid temporary strings Add deleted overloads for rvalue strings. - 2332: + 2332: regex_iterator/regex_token_iterator should forbid temporary regexes Add deleted constructors. - 2399: + 2399: shared_ptr's constructor from unique_ptr should be constrained Constrain the constructor to require convertibility. - 2400: + 2400: shared_ptr's get_deleter() should use addressof() Use addressof. - 2401: + 2401: std::function needs more noexcept Add noexcept to the assignment and comparisons. - 2407: + 2407: packaged_task(allocator_arg_t, const Allocator&, F&&) should neither be constrained nor explicit @@ -1012,74 +1014,74 @@ requirements of the license of GCC. Remove explicit from the constructor. - 2415: + 2415: Inconsistency between unique_ptr and shared_ptr Create empty an shared_ptr from an empty unique_ptr. - 2418: + 2418: apply does not work with member pointers Use mem_fn for member pointers. - 2440: + 2440: seed_seq::size() should be noexcept Add noexcept. - 2441: + 2441: Exact-width atomic typedefs should be provided Define the typedefs. - 2442: + 2442: call_once() shouldn't DECAY_COPY() Remove indirection through call wrapper that made copies of arguments and forward arguments straight to std::invoke. - 2454: + 2454: Add raw_storage_iterator::base() member Add the base() member function. - 2455: + 2455: Allocator default construction should be allowed to throw Make noexcept specifications conditional. - 2458: + 2458: N3778 and new library deallocation signatures Remove unused overloads. - 2459: + 2459: std::polar should require a non-negative rho Add debug mode assertion. - 2466: + 2466: allocator_traits::max_size() default behavior is incorrect Divide by the object type. - 2484: + 2484: rethrow_if_nested() is doubly unimplementable @@ -1087,21 +1089,21 @@ requirements of the license of GCC. ill-formed. - 2583: + 2583: There is no way to supply an allocator for basic_string(str, pos) Add new constructor - 2684: + 2684: priority_queue lacking comparator typedef Define the value_compare typedef. - 2770: + 2770: tuple_size<const T> specialization is not SFINAE compatible and breaks decomposition declarations @@ -1110,7 +1112,7 @@ requirements of the license of GCC. only use it if valid. - 2781: + 2781: Contradictory requirements for std::function and std::reference_wrapper @@ -1119,7 +1121,7 @@ requirements of the license of GCC. arguments and store them directly as the target object. - 2802: + 2802: Add noexcept to several shared_ptr related functions @@ -1127,14 +1129,14 @@ requirements of the license of GCC. Add noexcept. - 2873: + 2873: shared_ptr constructor requirements for a deleter Use rvalues for deleters. - 2942: + 2942: LWG 2873's resolution missed weak_ptr::owner_before