admin/mlib
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update issue

Browse Source
This commit is contained in:
Patrick Pelissier committed 2019-02-21 20:19:04 +01:00
1 parent 8e62537604
commit 97f80450ca
1 file changed
+7 -3
Download Patch File Download Diff File Expand all files Collapse all files
doc/ISSUES.org
+7 -3
View File
@@ -1,7 +1,7 @@
*Long term issues* *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 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 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 ** 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 compatible with a pure COPY semantic. An exported MOVE operator will tell
other containers than the type shall be carefully moved using the provided other containers than the type shall be carefully moved using the provided
MOVE operator. 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: * DONE #22: Enhanced services for SPSC Queue :ENHANCEMENT: