From 6d016d732be13fee8e3057d728c72c44c8b9028b Mon Sep 17 00:00:00 2001 From: Patrick Pelissier Date: Sun, 31 Mar 2019 22:37:00 +0200 Subject: [PATCH] Update tags --- doc/ISSUES.org | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/ISSUES.org b/doc/ISSUES.org index 56563e83..d5ccc951 100644 --- a/doc/ISSUES.org +++ b/doc/ISSUES.org @@ -1,7 +1,7 @@ *Long term issues* ------------------ -* TODO #23: Force MOVE semantic +* TODO #23: Force MOVE semantic :ENHANCEMENT: 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 @@ -16,7 +16,7 @@ moving the data before they can be moved using MOVE. Two solutions: - New operator MOVE_SELF to fix a type after it has been moved. - If MOVE defined, force another table and then copy by hand the type. This will be slower and consumme more memory. -** MOVE in OPLIST +** MOVE in OPLIST :ENHANCEMENT: 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 @@ -28,7 +28,7 @@ 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: Add services: