On Tuesday, 9 May 2017 at 13:30:49 UTC, Nordlöw wrote:
I'll write a Bugzilla issue later today.
https://issues.dlang.org/show_bug.cgi?id=17388
On Tuesday, 9 May 2017 at 12:25:29 UTC, Nordlöw wrote:
On Tuesday, 9 May 2017 at 11:52:35 UTC, Nordlöw wrote:
I've tagged the ref-returning functions (in this case
`opSlice`) with `return scope` for my statically allocated
array struct at
Here's a simpler example
On Tuesday, 9 May 2017 at 12:25:29 UTC, Nordlöw wrote:
On Tuesday, 9 May 2017 at 11:52:35 UTC, Nordlöw wrote:
I've tagged the ref-returning functions (in this case
`opSlice`) with `return scope` for my statically allocated
array struct at
Here's a simpler example
On Tuesday, 9 May 2017 at 11:52:35 UTC, Nordlöw wrote:
I've tagged the ref-returning functions (in this case
`opSlice`) with `return scope` for my statically allocated
array struct at
Here's a simpler example
I've tagged the ref-returning functions (in this case `opSlice`)
with `return scope` for my statically allocated array struct at
https://github.com/nordlow/phobos-next/blob/master/src/arrayn.d
but for some reason the scope-checking (via -dip1000) allows both