Re: Generalize .ptr to RawPtr ranges?

2015-10-06 Thread Dmitry Olshansky via Digitalmars-d
On 06-Oct-2015 01:36, Brad Anderson wrote: On Monday, 5 October 2015 at 10:06:04 UTC, Dmitry Olshansky wrote: Just a random idea - slices have .ptr and therefor have a bunch of advantages such as SSE optimized copy routine. Once I wrap a slice in something (anything) it looses ALL of that. Now

Re: Generalize .ptr to RawPtr ranges?

2015-10-05 Thread Brad Anderson via Digitalmars-d
On Monday, 5 October 2015 at 10:06:04 UTC, Dmitry Olshansky wrote: Just a random idea - slices have .ptr and therefor have a bunch of advantages such as SSE optimized copy routine. Once I wrap a slice in something (anything) it looses ALL of that. Now for instance

Re: Generalize .ptr to RawPtr ranges?

2015-10-05 Thread Jonathan M Davis via Digitalmars-d
On Monday, 5 October 2015 at 10:06:04 UTC, Dmitry Olshansky wrote: Just a random idea - slices have .ptr and therefor have a bunch of advantages such as SSE optimized copy routine. Once I wrap a slice in something (anything) it looses ALL of that. Now for instance

Generalize .ptr to RawPtr ranges?

2015-10-05 Thread Dmitry Olshansky via Digitalmars-d
Just a random idea - slices have .ptr and therefor have a bunch of advantages such as SSE optimized copy routine. Once I wrap a slice in something (anything) it looses ALL of that. Now for instance std.container.Array!int.Range can easily provide .ptr property, together with .length it would