Boost-Commit mailing page: [Boost-commit] svn:boost r51682

Date view	Thread view	Subject view	Author view

Subject: [Boost-commit] svn:boost r51682 - sandbox/committee/LWG
From: bdawes_at_[hidden]
Date: 2009-03-10 07:08:19

Next message: bdawes_at_[hidden]: "[Boost-commit] svn:boost r51683 - sandbox/committee/LWG"
Previous message: peder.holt_at_[hidden]: "[Boost-commit] svn:boost r51681 - trunk/boost/typeof/msvc"

Author: bemandawes
Date: 2009-03-10 07:08:18 EDT (Tue, 10 Mar 2009)
New Revision: 51682
URL: http://svn.boost.org/trac/boost/changeset/51682

Log:
Add Peter Dimov comments
Text files modified:
sandbox/committee/LWG/LWG_0xCD1_status.html | 101 ++++++++++++++++-----------------------
1 files changed, 41 insertions(+), 60 deletions(-)

Modified: sandbox/committee/LWG/LWG_0xCD1_status.html
==============================================================================
--- sandbox/committee/LWG/LWG_0xCD1_status.html (original)
+++ sandbox/committee/LWG/LWG_0xCD1_status.html 2009-03-10 07:08:18 EDT (Tue, 10 Mar 2009)
@@ -21,7 +21,7 @@
<h1>Library Working Group 
Status of CD1 National Body Comments</h1>
Revised:
-09 Mar 2009 02:59:59 PM -0500
+09 Mar 2009 08:41:27 PM -0500

Disposition [Being reviewed by Editor] has been applied all Type Ed comments
which do not have a specific response from a sub-group.
@@ -4098,33 +4098,30 @@

 Agree. Forward to the project editor.</tr>
 <tr>
- <td>
- US 72
+ <td valign="top">
+ <a name="US72">US 72</a>

- <td>
+ <td valign="top">
 20.6.12 [func.bind. 
- bind]<td>
+ bind]<td valign="top">
 

- <td>
+ <td valign="top">
 te

- <td>
+ <td valign="top">
 
 bind should support move-only functors and bound arguments.

- 
-
- <td>
- 
-
- <td>
+ <td valign="top">
+  <td valign="top">
 We look forward to a paper on this topic. We recommend
 no action until a paper is available. We do think that bind would
 require further overloads to support move semantics, if indeed move
- semantics are possible. 
-
- </tr>
+ semantics are possible.Peter Dimov comments: I believe
+ that what is meant here is that the CopyConstructible requirements on F
+ and BoundArgs must be changed to MoveConstructible. I see no need for a
+ paper.</tr>
 <tr>
 <td valign="top">
 JP 38
@@ -4142,10 +4139,7 @@
 <td valign="top">
 
- add the move requirement for bind's return type. 
- 
-
- 
 For example, assume following th1 and th2,

@@ -4192,7 +4186,12 @@
 [NOTE: We would like to see a clarification of the wording for Returnable<t>
 that makes it clear that move-only types can be Returnable.] </t>

- </tr>
+ 
+
+ Peter Dimov comments: I believe that if US 72 is
+ resolved as proposed by me above, the objects returned by bind will already
+ be required to have a move constructor, otherwise bind would be unable to
+ return them when F or a type in BoundArgs is move-only.</tr>
 <tr>
 <td valign="top">
 DE-21
@@ -4727,9 +4726,7 @@
 <td>
 std::hash should
 be implemented for much more of the standard library. In
- particular for pair, tuple and all the standard containers.
-
- 
+ particular for pair, tuple and all the standard containers. 

 <td>
 .
@@ -4768,7 +4765,13 @@
 

 We look forward to a paper on this topic. We recommend no action until a
- paper is available. We understand that a paper is forthcoming.<tr valign="top">
+ paper is available. We understand that a paper is forthcoming.
+
+ Peter Dimov comments: shared_ptr<T> and weak_ptr<T> support all types T for
+ which T* is valid. In other words, a possible (partial) resolution is to
+ change class T to PointeeType T for shared_ptr, weak_ptr and possibly
+ enable_shared_from_this. 
+ <tr valign="top">
 <td>
 UK 
 213
@@ -4790,9 +4793,7 @@
 match. The Allocator concept allows for a wider variety of
 allocators that users may choose to supply if their
 allocation model does not require operator new, without
- impacting the requirements of this template.
-
- 
+ impacting the requirements of this template. 

 <td>
 The primary allocator template should be
@@ -4822,9 +4823,7 @@
 <td>
 
 raw_storage_iterator needs constraining as an iterator
- adaptor to be safely used in constrained templates
-
- 
+ adaptor to be safely used in constrained templates 

 <td>
 Constrain the raw_storage_iterator template
@@ -4937,39 +4936,27 @@
 large increase in the number of pair and tuple constructors

 23: confusing
- “AllocatableElement” requirements throughout.
-
- 
+ “AllocatableElement” requirements throughout. 

 <td>
 Remove support
 for scoped allocators from the working paper. This includes
- at least the following changes:
-
- 
+ at least the following changes: 

 Remove 20.8.3
- [allocator.element.concepts]
-
- 
+ [allocator.element.concepts] 

 Remove 20.8.7
- [allocator.adaptor]
-
- 
+ [allocator.adaptor] 

 Remove 20.8.10
- [construct.element]
-
- 
+ [construct.element] 

 In Clause 23:
 replace requirements naming the AllocatableElement concept
 with requirements naming CopyConstructible,
 MoveConstructible, DefaultConstructible, or Constructible,
- as appropriate.
-
- 
+ as appropriate. 

 <td>
 Resolved by
@@ -5099,8 +5086,6 @@
 <td>
 
 Correct as follows.
-
- 
 

 
@@ -5132,8 +5117,6 @@
 typename
 allocator_type = T::allocator_type;
-
- 
 

 <td>
@@ -5203,9 +5186,7 @@
 traits (20.8.4), the complexity of copy and move operations
 can be constant or linear time. This level of customization
 greatly increases the complexity of standard containers,
- and benefits only a tiny fraction of the C++ community.
-
- 
+ and benefits only a tiny fraction of the C++ community. 

 <td>
 Remove 20.8.4.
@@ -5256,7 +5237,9 @@
 <td>
 We look forward to
 a paper on this topic. We recommend no action until a paper is
- available. We believe that the shared pointer must use the default deleter for the conversion to succeed. 
+ available. We believe that the shared pointer must use the default deleter for the conversion to succeed.
+ Peter Dimov comments: this is basically a request for shared_ptr<>::release
+ in disguise, with all the associated problems. Not a good idea. 

 <tr valign="top">
 <td>
@@ -5289,9 +5272,7 @@

 
 unique_ptr<int, void(*)(void*)>
- p(malloc(sizeof(int)), free);  // ok
-
- 
+ p(malloc(sizeof(int)), free);  // ok 

 <td>

Next message: bdawes_at_[hidden]: "[Boost-commit] svn:boost r51683 - sandbox/committee/LWG"
Previous message: peder.holt_at_[hidden]: "[Boost-commit] svn:boost r51681 - trunk/boost/typeof/msvc"

Date view	Thread view	Subject view	Author view