[Issue 15932] Get rid of the implicit slicing of static arrays

[d-bugmail at puremagic.com]

https://issues.dlang.org/show_bug.cgi?id=15932

hsteoh at qfbox.info changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #3 from hsteoh at qfbox.info ---
(In reply to RazvanN from comment #2)
> If you annotate the functions with @safe then you get:
> 
> test.d(9): Deprecation: reference to local variable `data` assigned to
> non-scope parameter `_data` calling `this`

That's good to know.


> I think that having the compiler automatically slice your static arrays is
> actually quite nice as you have to type less.

I disagree, the compiler implicitly slicing your static arrays for you has the
same sort of issues as implicit constructions in C++: they tend to turn up
where they are unexpected and cause problems.


> The fact that you can escape a
> pointer to an expired stack frame is something that @safe and scope should
> deal with. Still, in system code this should be perfectly fine.

How can escaping a pointer to an expired stack frame ever be fine??  That is
never OK and should not be allowed in the language. At least, not implicitly.
If you want to explicitly escape a reference to a local static array, you
should be forced to explicitly slice it, not have the compiler silently insert
it for you.

--