[Issue 16526] @safe code should do null check for members when appropriate

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

[Issue 16526] @safe code should do null check for members when appropriate

2016-09-22 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16526 --- Comment #3 from Steven Schveighoffer --- (In reply to Sobirari Muhomori from comment #1) > struct S > { > byte[3000] a,b; > } > void f(ref S s) > { > g(s.b); > } Actually, technically this could trigger a check of s address, since b'

[Issue 16526] @safe code should do null check for members when appropriate

2016-09-22 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16526 --- Comment #2 from Steven Schveighoffer --- Yes, this is what I meant by "There are still ways to access data beyond one page without incurring a check with this scheme, but we are talking about very weird and rare code." --

[Issue 16526] @safe code should do null check for members when appropriate

2016-09-22 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16526 Sobirari Muhomori changed: What|Removed |Added Hardware|x86 |All OS|Mac OS X