add non-stencil algorithm specializations for InputIterator correctness

lion03 / thrust

Automatically exported from code.google.com/p/thrust

Apache License 2.0

0 stars 0 forks source link

add non-stencil algorithm specializations for InputIterator correctness #419

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

Since InputIterators can't be dereferenced multiple times we shouldn't 
implement algorithms like copy_if(first, last, output, pred) with 
copy_if(first, last, first, output, pred).

In general the unit tests should check InputIterator semantic correctness.

Original issue reported on code.google.com by wnbell on 7 Dec 2011 at 8:36

GoogleCodeExporter commented 8 years ago

Original comment by wnbell on 5 Feb 2012 at 11:26

Added labels: Milestone-Release1.7
Removed labels: Milestone-Release1.6

GoogleCodeExporter commented 8 years ago

Forwarded to https://github.com/thrust/thrust/issues/55

Original comment by jaredhoberock on 7 May 2012 at 8:58

Changed state: Forwarded