# Difference between revisions of "To Do List"

SeanParent (Talk | contribs) (→Non-Mutating Algorithms) |
SeanParent (Talk | contribs) |
||

Line 145: | Line 145: | ||

--- | --- | ||

+ | |||

+ | (notes from conversation about removing get_value() from dictionary.hpp and providing a generalized form). | ||

+ | |||

+ | Sean Parent | ||

+ | So - current summary and action items: | ||

+ | Sean Parent | ||

+ | 1) get_value() in dictionary.hpp becomes deprecated next release (hmm - move to a deprecated namespace?) in favor of new algorithms. | ||

+ | 3:38 PM | ||

+ | Sean Parent | ||

+ | 2) We add: | ||

+ | I find_at(I f, I l, const T&, P); | ||

+ | [along with all range variants and specialize for associative containers - P defaults to identity if value_type(I) == P) | ||

+ | Sean Parent | ||

+ | otherwise P defaults to get_element<0> (or whatever the name is in adobe/functional.hpp) | ||

+ | Sean Parent | ||

+ | 3) consider that get_element<0> should have a default implementation of identity to normalize the case. | ||

+ | Sean Parent | ||

+ | 4) similarly provide find_value_at() and assign_at() | ||

+ | |||

+ | U& find_value_at(I, I, T, P); | ||

+ | I assign_at(I, I, T, U&, P); | ||

+ | |||

+ | Sean Parent | ||

+ | 5) review exisiting find() algorithms to see which it would also make sense to refine for containers (i.e. find() ) | ||

+ | The AIM service could not send the message: A message or picture is too large to be transmitted. | ||

+ | Sean Parent | ||

+ | 6) Add an is_associative_container<> trait so we can automatically pick up new ASL containers and can be made to work with user containers. | ||

== Notes == | == Notes == | ||

Check to see which intrinsics (like multiply returning long result) are in C99 | Check to see which intrinsics (like multiply returning long result) are in C99 |

## Revision as of 22:52, 16 April 2008

## Contents

## Goals

We are now in a mode of completing the core of ASL (defined to be roughly the libraries which make of the property model and layout libraries as well as anything which is complete enough to warrant inclusion).

To that end, we are reviewing all of the libraries and for each one determining:

- Is it used and/or useful and worth being completed. If not it will either be removed all together or partitioned into the platform libraries for later consideration.
- What is necessary to complete the space to create a completed body of work.

We are working to restructure the documentation to include the "final" set of libraries and to flesh out the documentation, test cases, and in some cases, the code.

## Algorithms

- every file where we shadow the std functions should go ahead and move the std function into the adobe namespace.

### Non-Mutating Algorithms

Order Selection Networks - Rework pin, min, max, median_3, median_5, select_ith_n

Review chapter from book (4)

For each provide a comparison based, const, and non-const versions.

Go to how many elements?

Definitions: select_ith_n: return the ith element in non-descending order out of n elements.

The network is minimal in the worst case if it does the minimum number of comparisons in the worst case and minimal in the average case if it does the minimum number of comparisons on average.

The selection network is stable if the retuned element is selected out of n elements stably soreted in non-decending order (we do not do sorting).

A selection network from partially ordered inputs is a selection network where a certain partial ordering of the elements is already determined.

[We need to develop a naming convention for paritial ordering.]

Question - do we provide sorting networks?

- [done] Removed bound_if - replaced with key_function form of lower/upper_bound.

Write a proper partition() (ordering and for forward iterator), partition_point_n(), and is_partitioned.

Make cautionary note about wrapped standard algorithms.

non_strict_order_partition(range, element, strict_weak_ordering) arranges it so that elements are not greater followed by elements which are not less.

- [done] Pull count_min/max_element. Replace with two passes - max_element(), count().

Binary searches

Write a better binary_search which returns lower_bound() if exists else last.

Write an adaptor for is_in_sorted_range - set_member?

find_first_of_set() - becomes find_if with adaptor.

We should try to adapt binary search algorithms such as upper bound and lower bound to work on sets and multisets.

### Finding and Counting

- [done] rename find_not_equal to find_not.

Extending find() - also provide find_not() and count_if_not() and count_not(). exists, none, all?

Check what other adobe/STL algorithms take unary predicates (partition_not?).

Versions of find and count need to take a binary predicate - see find_match().

And find_n(), count_n() for all versions.

Versions of for_each for_each_value() - rename of for_each_position() for_each_value_n() for_each_n()

Sorting Group is_sorted sorted() rename to sorted_run()

mismatch() gets grouped with equal() and search() Add mismatch_n().

Look at reduce accumulate and related functions - do we keepr reduce_balanced()?

## Mutating Algorithms

-- copy family

Try to simply use the name copy() for copy_bound() - etc.

Add bounded forms of other functions, i.e. swap_ranges.

Also applies to find and count

copy I I 0 copy_b I I F F copy_n I n O copy_b I I O n copy_b I n F F copy_b I F F

I I n F F

--- tranform_if replaces filter by splitting the function object.

transform_if_not.

Also add _if forms for other functions.

Also have copy_if and copy_if_not (as replacement of remove). --- Explore iota and fit more into the copy notation.

With a value for increment - ---

It looks like remove_runs and mutate_runs are not used - remove them.

---

Add a reverse group and add reverse_until.

---

Remove the pair return from rotate and simply return m'

---

(notes from conversation about removing get_value() from dictionary.hpp and providing a generalized form).

Sean Parent So - current summary and action items: Sean Parent 1) get_value() in dictionary.hpp becomes deprecated next release (hmm - move to a deprecated namespace?) in favor of new algorithms. 3:38 PM Sean Parent 2) We add: I find_at(I f, I l, const T&, P); [along with all range variants and specialize for associative containers - P defaults to identity if value_type(I) == P) Sean Parent otherwise P defaults to get_element<0> (or whatever the name is in adobe/functional.hpp) Sean Parent 3) consider that get_element<0> should have a default implementation of identity to normalize the case. Sean Parent 4) similarly provide find_value_at() and assign_at()

U& find_value_at(I, I, T, P); I assign_at(I, I, T, U&, P);

Sean Parent 5) review exisiting find() algorithms to see which it would also make sense to refine for containers (i.e. find() ) The AIM service could not send the message: A message or picture is too large to be transmitted. Sean Parent 6) Add an is_associative_container<> trait so we can automatically pick up new ASL containers and can be made to work with user containers.

## Notes

Check to see which intrinsics (like multiply returning long result) are in C99