From 97f80450ca99dd595934fba4d582cacff6983baf Mon Sep 17 00:00:00 2001 From: Patrick Pelissier Date: Thu, 21 Feb 2019 20:19:04 +0100 Subject: [PATCH] Update issue --- doc/ISSUES.org | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/doc/ISSUES.org b/doc/ISSUES.org index 1ec4e6cc..56563e83 100644 --- a/doc/ISSUES.org +++ b/doc/ISSUES.org @@ -1,7 +1,7 @@ *Long term issues* ------------------ -* #23: Force MOVE semantic +* TODO #23: Force MOVE semantic Some type may need to have a force MOVE semantic (for example, they can store pointer to themselves). Currently the INIT_MOVE & MOVE operators are more @@ -18,12 +18,16 @@ moving the data before they can be moved using MOVE. Two solutions: ** MOVE in OPLIST -Proposal: do not export MOVE operator in OPLIST if the MOVE operator is +Proposal: do not export INIT_MOVE / MOVE operator in OPLIST if the MOVE operator is compatible with a pure COPY semantic. An exported MOVE operator will tell other containers than the type shall be carefully moved using the provided MOVE operator. -INIT_MOVE is probably safe. +For example for tuple, it shall + +- create an init_move operator if no one has disabled INIT_MOVE, +- export the init_move operator if at least one has exported a INIT_MOVE and no one has disabled INIT_MOVE. + * DONE #22: Enhanced services for SPSC Queue :ENHANCEMENT: