[Issue 19965] [DIP1000] Template allows to escape internal pointer

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

[Issue 20149] [DIP1000] Local data escapes `opSlice` if not annotated with `return`

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

[Issue 20149] [DIP1000] Local data escapes `opSlice` if not annotated with `return`

2019-08-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20149 --- Comment #4 from Mike Franklin --- > Removing all templating from the example above cause the compiler to emit > what I think is correct behavior: That may mean this is a duplicate of Issue 19965, but I'm not sure. --

[Issue 20149] [DIP1000] Local data escapes `opSlice` if not annotated with `return`

2019-08-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20149 --- Comment #3 from Mike Franklin --- Removing all templating from the example above cause the compiler to emit what I think is correct behavior: --- import std.stdio; @safe: struct ScopeBuffer { this(char[4] buf, size_t len = 0) {

[Issue 20149] [DIP1000] Local data escapes `opSlice` if not annotated with `return`

2019-08-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20149 --- Comment #2 from Mike Franklin --- Interestingly removing the `inout` attribution on `opSlice` causes the compiler to emit an error at the return statement in `fun`. I think the error should instead be emitted at the return statement of

[Issue 20149] [DIP1000] Local data escapes `opSlice` if not annotated with `return`

2019-08-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20149 --- Comment #1 from Mike Franklin --- > Observation-2: Decorating `opSlice` with `return` causes a compiler error to > be correctly emitted where the slice is escaping `foo` In the example above, that should be `fun`, not `foo`. --

[Issue 20149] New: [DIP1000] Local data escapes `opSlice` if not annotated with `return`

2019-08-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20149 Issue ID: 20149 Summary: [DIP1000] Local data escapes `opSlice` if not annotated with `return` Product: D Version: D2 Hardware: All OS: All Status:

[Issue 20149] [DIP1000] Local data escapes `opSlice` if not annotated with `return`

2019-08-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20149 Mike Franklin changed: What|Removed |Added Keywords||safe --

[Issue 19175] @safe code can escape local array references

2019-08-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=19175 Mike Franklin changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Issue 20141] No builtin version which says if the platform is 64bit

2019-08-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20141 --- Comment #3 from Manu --- Yes... thanks for that information, that's exactly why I made the point. --

[Issue 20137] A program crashes at runtime (should be compile error)

2019-08-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20137 --- Comment #3 from Victor Porton --- This "by design" is very disgracing. Need to do something. If to make it more reliable it's needed compiler changes, a new compiler "directive" should be added. @safe being missing should make harmlessly

[Issue 340] [Tracker] Forward reference bugs and other order-of-declaration issues

2019-08-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=340 RazvanN changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Issue 1547] Default parameter values should use implicit static opCall

2019-08-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=1547 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #2 from Dlang Bot ---

[Issue 1536] Literal '0' is improperly used to deduce an implicit template parameter

2019-08-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=1536 RazvanN changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 1515] compiler accepts invalid template declaration

2019-08-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=1515 RazvanN changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 1514] mixin doesn't make the template to "function template"

2019-08-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=1514 RazvanN changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 9983] inout type can not be used as a parameter for structure template

2019-08-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=9983 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-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 20141] No builtin version which says if the platform is 64bit

2019-08-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20141 --- Comment #2 from anonymous4 --- See also https://github.com/dlang/druntime/blob/master/src/core/sys/posix/sys/types.d#L45 --

[Issue 20141] No builtin version which says if the platform is 64bit

2019-08-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20141 --- Comment #1 from anonymous4 --- Pointers are 32bit on x32, it's the sole purpose of x32. --

[Issue 20137] A program crashes at runtime (should be compile error)

2019-08-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20137 anonymous4 changed: What|Removed |Added Keywords||safe Status|NEW

[Issue 1104] CodeView: char is marked 0x20 (T_UCHAR) instead of 0x10 (T_CHAR)

2019-08-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=1104 Dlang Bot changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Issue 20148] void initializated bool can be both true and false

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

[Issue 4372] type of enumerator values reduced to base type in debug info

2019-08-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=4372 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #7 from Dlang Bot --- @rainers

[Issue 982] Codeview: symbols of enum type are declared integer

2019-08-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=982 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #3 from Dlang Bot --- @rainers

[Issue 1104] CodeView: char is marked 0x20 (T_UCHAR) instead of 0x10 (T_CHAR)

2019-08-21 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=1104 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #10 from Dlang Bot ---