[Issue 15651] filter: only parameters or stack based variables can be inout

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15651 Iain Buclaw changed: What|Removed |Added Priority|P1 |P3 --

[Issue 15651] filter: only parameters or stack based variables can be inout

2021-03-19 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15651 anonymous4 changed: What|Removed |Added See Also||https://issues.dlang.org/sh

[Issue 15651] filter: only parameters or stack based variables can be inout

2019-08-29 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15651 --- Comment #8 from anonymous4 --- If you want the mutable ranges to process inout data, they should be able to return inout data unless you want to do the front(inout collection) thing. --

[Issue 15651] filter: only parameters or stack based variables can be inout

2019-08-28 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15651 --- Comment #7 from Steven Schveighoffer --- (In reply to Harry Vennik from comment #6) > /* inout resolves to mutable in call to getRef */ > c.getRef(5) = 8; // Undefined behavior That would fail because c.getRef(5) would return ref

[Issue 15651] filter: only parameters or stack based variables can be inout

2019-08-25 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15651 --- Comment #6 from Harry Vennik --- (In reply to Steven Schveighoffer from comment #3) > In fact, we should allow inout to be used ANYWHERE, except global variables > (as putting inout variables in global space can change the meaning from call > to

[Issue 15651] filter: only parameters or stack based variables can be inout

2019-08-24 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15651 --- Comment #5 from Harry Vennik --- (In reply to Steven Schveighoffer from comment #3) > I'd try my hand at an inout improvement DIP, but I feel it would likely be > rejected on principle, since inout is so disfavored by leadership. I already have

[Issue 15651] filter: only parameters or stack based variables can be inout

2019-08-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15651 --- Comment #4 from anonymous4 --- It will need separation between collections and iterators --- struct A { int[][] a; inout(int[])[] f() inout { return a.filter(x=>x!=null).array; } }

[Issue 15651] filter: only parameters or stack based variables can be inout

2019-08-22 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15651 Steven Schveighoffer changed: What|Removed |Added CC||schvei...@yahoo.com --- Comment #3

[Issue 15651] filter: only parameters or stack based variables can be inout

2019-08-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15651 anonymous4 changed: What|Removed |Added See Also||https://issues.dlang.org/sh

[Issue 15651] filter: only parameters or stack based variables can be inout

2019-08-16 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15651 Simen Kjaeraas changed: What|Removed |Added CC||simen.kja...@gmail.com

[Issue 15651] filter: only parameters or stack based variables can be inout

2019-08-14 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15651 Harry Vennik changed: What|Removed |Added CC||htven...@gmail.com --

[Issue 15651] filter: only parameters or stack based variables can be inout

2018-04-18 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15651 Alex changed: What|Removed |Added CC||sascha.or...@gmail.com --