On Wednesday, 22 June 2016 at 13:36:54 UTC, Marc Schütz wrote:
On Tuesday, 21 June 2016 at 19:21:01 UTC, Gary Willoughby wrote:
Right ok, thanks! It doesn't seem to help though as the
compiler complains about it being not @nogc.
You probably need to declare the delegate and opApply() itself
a
On Tuesday, 21 June 2016 at 19:21:01 UTC, Gary Willoughby wrote:
Right ok, thanks! It doesn't seem to help though as the
compiler complains about it being not @nogc.
You probably need to declare the delegate and opApply() itself as
@nogc, too:
int opApply(scope int delegate(int) @nogc dg) @n
On Tuesday, 21 June 2016 at 12:53:11 UTC, Adam D. Ruppe wrote:
On Tuesday, 21 June 2016 at 12:48:04 UTC, Gary Willoughby wrote:
I have no idea what that means. Can anyone shed more light on
this, please?
So when you use local variables in a delegate, the compiler
usually makes a copy of them
On Tuesday, 21 June 2016 at 12:48:04 UTC, Gary Willoughby wrote:
I have no idea what that means. Can anyone shed more light on
this, please?
So when you use local variables in a delegate, the compiler
usually makes a copy of them just in case the delegate gets saved
for later.
When you mark
On Monday, 20 June 2016 at 15:27:32 UTC, Adam D. Ruppe wrote:
On Monday, 20 June 2016 at 15:13:53 UTC, Gary Willoughby wrote:
I think the problem is that the delegate which is required by
opApply is allocated using the GC.
make the delegate in opApply scope
int opApply(scope int delegate(what
On Monday, 20 June 2016 at 15:47:44 UTC, Gary Willoughby wrote:
On Monday, 20 June 2016 at 15:27:32 UTC, Adam D. Ruppe wrote:
On Monday, 20 June 2016 at 15:13:53 UTC, Gary Willoughby wrote:
I think the problem is that the delegate which is required by
opApply is allocated using the GC.
make t
On Monday, 20 June 2016 at 15:27:32 UTC, Adam D. Ruppe wrote:
On Monday, 20 June 2016 at 15:13:53 UTC, Gary Willoughby wrote:
I think the problem is that the delegate which is required by
opApply is allocated using the GC.
make the delegate in opApply scope
int opApply(scope int delegate(what
On Monday, 20 June 2016 at 15:13:53 UTC, Gary Willoughby wrote:
I think the problem is that the delegate which is required by
opApply is allocated using the GC.
make the delegate in opApply scope
int opApply(scope int delegate(whatever) dg)
On Monday, 20 June 2016 at 14:34:33 UTC, Mathias Lang wrote:
Can't `opApply` with `auto` return type works since it infers
attributes ?
I think the problem is that the delegate which is required by
opApply is allocated using the GC.
On Monday, 20 June 2016 at 14:08:58 UTC, Gary Willoughby wrote:
Is there any way to make opApply @nogc? or provide the same
foreach functionality without implementing a range interface?
I want to iterate over a piece of memory using a pointer. I
thought about using opSlice but that doesn't pro
Is there any way to make opApply @nogc? or provide the same
foreach functionality without implementing a range interface?
I want to iterate over a piece of memory using a pointer. I
thought about using opSlice but that doesn't provide information
for an index in a foreach loop.
auto opSlice(
11 matches
Mail list logo