Issue |
Status |
Section |
Title |
Proposed Resolution |
Duplicates |
Last modified |
2114 |
New |
17.6.3.3 [nullablepointer.requirements] |
Incorrect "contextually convertible to bool" requirements |
Yes |
|
2012-01-14 |
2081 |
New |
17.6.3.5 [allocator.requirements] |
Allocator requirements should include CopyConstructible |
Yes |
|
2012-01-14 |
2108 |
New |
17.6.3.5 [allocator.requirements] |
No way to identify allocator types that always compare equal |
Yes |
|
2012-01-14 |
2016 |
Open |
17.6.3.5 [allocator.requirements] |
Allocators must be no-throw swappable |
Yes |
|
2012-01-14 |
2112 |
New |
17.6.5 [conforming] |
User-defined classes that cannot be derived from |
No |
|
2012-01-14 |
2113 |
New |
17.6.5 [conforming] |
Do library implementers have the freedom to add final to non-polymorphic components? |
No |
|
2012-01-14 |
1526 |
Deferred |
17.6.5.9 [res.on.data.races] |
[FCD] C++ should not impose thread safety requirements on C99 library implementations |
No |
|
2012-01-14 |
Issue |
Status |
Section |
Title |
Proposed Resolution |
Duplicates |
Last modified |
2103 |
New |
20.6.9 [default.allocator] |
std::allocator_traits<std::allocator<T>>::propagate_on_container_move_assignment |
Yes |
|
2012-01-14 |
2089 |
New |
20.6.9.1 [allocator.members] |
std::allocator::construct should use uniform initialization |
Yes |
|
2012-01-14 |
2072 |
New |
20.6.11 [temporary.buffer] |
Unclear wording about capacity of temporary buffers |
No |
|
2012-01-14 |
2118 |
New |
20.7.1.3 [unique.ptr.runtime] |
unique_ptr for array does not support cv qualification conversion of actual argument |
Yes |
|
2012-01-14 |
2070 |
Open |
20.7.2.2.6 [util.smartptr.shared.create] |
allocate_shared should use allocator_traits<A>::construct |
Yes |
|
2012-01-14 |
2083 |
New |
20.7.2.3 [util.smartptr.weak] |
const-qualification on weak_ptr::owner_before |
Yes |
|
2012-01-14 |
2048 |
Review |
20.8 [function.objects] |
Unnecessary mem_fn overloads |
Yes |
|
2012-01-14 |
2062 |
Open |
20.8.11.2 [func.wrap.func] |
Effect contradictions w/o no-throw guarantee of std::function swaps |
No |
|
2012-01-14 |
2119 |
New |
20.8.12 [unord.hash] |
Missing hash specializations for extended integer types |
Yes |
|
2012-01-14 |
2049 |
Review |
20.9.4.3 [meta.unary.prop] |
is_destructible is underspecified |
Yes |
|
2012-01-14 |
2077 |
New |
20.9.4.3 [meta.unary.prop] |
Further incomplete constraints for type traits |
No |
|
2012-01-14 |
2116 |
New |
20.9.4.3 [meta.unary.prop] |
std::swap noexcept(what?) |
No |
|
2012-01-14 |
2101 |
New |
20.9.7 [meta.trans] |
Some transformation types can produce impossible types |
Yes |
|
2012-01-14 |
2094 |
New |
20.11.5.1 [time.duration.cons] |
duration conversion overflow shouldn't participate in overload resolution |
Yes |
|
2012-01-14 |
2054 |
Open |
20.11.6 [time.point] |
time_point constructors need to be constexpr |
Yes |
|
2012-01-14 |
2057 |
Open |
20.11.6.5 [time.point.nonmember] |
time_point + duration semantics should be made constexpr conforming |
Yes |
|
2012-01-14 |
Issue |
Status |
Section |
Title |
Proposed Resolution |
Duplicates |
Last modified |
2105 |
New |
23.2.1 [container.requirements.general] |
Inconsistent requirements on const_iterator's value_type |
Yes |
|
2012-01-14 |
2052 |
Open |
23.2.4 [associative.reqmts] |
Mixup between mapped_type and value_type for associative containers |
Yes |
|
2012-01-14 |
1175 |
Review |
23.2.5 [unord.req] |
unordered complexity |
Yes |
|
2012-01-14 |
2123 |
New |
23.3.4.6 [forwardlist.ops] |
merge() allocator requirements for lists versus forward lists |
Yes |
|
2012-01-16 |
2122 |
New |
23.3.5.5 [list.ops] |
merge() stability for lists versus forward lists |
Yes |
|
2012-01-16 |
2066 |
Tentatively Resolved |
23.3.6.3 [vector.capacity] |
Missing specification of vector::resize(size_type) |
Yes |
|
2012-01-14 |
2012 |
Open |
23.4 [associative] |
Associative maps should insert pair, not tuple |
Yes |
|
2012-01-14 |
2059 |
Review |
23.4.4 [map] |
C++0x ambiguity problem with map::erase |
Yes |
|
2012-01-14 |
2005 |
Review |
23.4.4.4 [map.modifiers] |
unordered_map::insert(T&&) protection should apply to map too |
Yes |
|
2012-01-14 |
2076 |
New |
23.4.6.2 [set.cons] |
Bad CopyConstructible requirement in set constructors |
Yes |
|
2012-01-14 |
Issue |
Status |
Section |
Title |
Proposed Resolution |
Duplicates |
Last modified |
2090 |
New |
30.4.1.2 [thread.mutex.requirements.mutex] |
Minor Overconstraint in Mutex Types |
No |
|
2012-01-14 |
2091 |
New |
30.4.1.3 [thread.timedmutex.requirements] |
Misplaced effect in m.try_lock_for() |
No |
|
2012-01-14 |
2104 |
New |
30.4.2.2 [thread.lock.unique] |
unique_lock move-assignment should not be noexcept |
Yes |
|
2012-01-14 |
2080 |
New |
30.4.4 [thread.once] |
Specify when once_flag becomes invalid |
No |
|
2012-01-14 |
2093 |
New |
30.5.1 [thread.condition.condvar] |
Throws clause of condition_variable::wait with predicate |
Yes |
|
2012-01-14 |
2092 |
New |
30.5.2 [thread.condition.condvarany] |
Vague Wording for condition_variable_any |
No |
|
2012-01-14 |
2102 |
Tentatively Ready |
30.6.1 [futures.overview] |
Why is std::launch an implementation-defined type? |
Yes |
|
2012-01-14 |
2056 |
Review |
30.6.1 [futures.overview] |
future_errc enums start with value 0 (invalid value for broken_promise) |
Yes |
|
2012-01-14 |
2095 |
New |
30.6.5 [futures.promise] |
promise and packaged_task missing constructors needed for uses-allocator construction |
Yes |
|
2012-01-14 |
2098 |
New |
30.6.5 [futures.promise] |
Minor Inconsistency between promise::set_value and promise::set_value_at_thread_exit |
Yes |
|
2012-01-14 |
2096 |
Tentatively Ready |
30.6.6 [futures.unique_future] |
Incorrect constraints of future::get in regard to MoveAssignable |
Yes |
|
2012-01-14 |
2078 |
New |
30.6.8 [futures.async] |
Throw specification of async() incomplete |
No |
|
2012-01-14 |
2100 |
New |
30.6.8 [futures.async] |
timed waiting functions cannot timeout if launch::async policy used |
Yes |
|
2012-01-14 |
2120 |
New |
30.6.8 [futures.async] |
What should async do if neither 'async' nor 'deferred' is set in policy? |
No |
|
2012-01-14 |
2097 |
New |
30.6.9.1 [futures.task.members] |
packaged_task constructors should be constrained |
Yes |
|
2012-01-14 |