Closed GoogleCodeExporter closed 8 years ago
My initial reaction is that we should prohibit overlapping stencil and value
ranges, since (1) there's no general-purpose way to detect overlap cheaply and
(2) handling the overlap case requires additional copies, which will slow down
the more common usage.
Original comment by wnbell
on 12 Jan 2011 at 12:31
My two cents: If the documentation simply stated that overlapping stencil and
value ranges are not supported, I would not have attempted this in the first
place. In general I would encourage the library to avoid as much internal
memory allocation as possible and leave the burden on the user to ensure that
there is no overlap.
Original comment by andrew.c...@gmail.com
on 12 Jan 2011 at 1:09
This issue was closed by revision 4b917f8138.
Original comment by wnbell
on 8 Feb 2011 at 6:01
Original issue reported on code.google.com by
wnbell
on 12 Jan 2011 at 12:20