boostorg/fusion
1
0
Fork 1
mirror of https://github.com/boostorg/fusion.git synced 2025-07-16 13:52:24 +02:00
Code Issues Packages Projects Releases Wiki Activity

mo' to do

Browse Source 
[SVN r37258]
This commit is contained in:
Tobias Schwinger
2007-03-21 19:31:13 +00:00
parent 1a1b40925b
commit 0c3a766ee8
1 changed files with 23 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
todo.txt
View File

@ -20,6 +20,9 @@
-- shall we consider container-type preserving variations of the -- shall we consider container-type preserving variations of the
functions/algorithms? functions/algorithms?
How about making joint_view Concept preserving? This way push/pop/front/back
will return a view of the same Concept. - tosh
* map_tie is implemented. It seems not yet documented? * map_tie is implemented. It seems not yet documented?
* multi_set, multi_map? * multi_set, multi_map?
@ -67,6 +70,26 @@
* Why do we need to set FUSION_MAX_VECTOR_SIZE when we set * Why do we need to set FUSION_MAX_VECTOR_SIZE when we set
FUSION_MAX_MAP_SIZE? FUSION_MAX_MAP_SIZE?
tosh:
* Document Incrementable / Single Pass Concepts
* Provide infinity-aware default implementation for Incrementable Sequences
Thoughts: It would probably be cleaner to have infinity conceptually
orthogonal so there can be infinite Bidi/RA/Assoc Sequences.
OTOH it complicates things in way that might not be worth it...
* Document new Concept-preserving semantics of iterator_range
* Document forgotten Concept preserving semantics of zip_view
* Implement always_view/always with repetitive_view<single_view<T> >
semantics - using repetitive_view will for this purpose will be way
too much overhead.
? Functional wrappers for intrinsics/algorithms.
* Rewrite functional benchmark
========================================================== ==========================================================
From the fusion review (please mark all done items): From the fusion review (please mark all done items):