[Issue 16394] TypeInfo.init() for static arrays returns single element instead of whole array

[via Digitalmars-d-bugs]

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

--- Comment #8 from Steven Schveighoffer <schveiguy at yahoo.com> ---
(In reply to ag0aep6g from comment #7)
> I.e., it's a long-standing bug.

Or functioning as designed, just not properly documented.

> Pretty much every bug fix can be considered a breaking change. I don't think
> we need to live with this, just because someone may be relying on behavior
> that's clearly going against documentation.

This part of TypeInfo is meant to be used internally. I don't think this corner
case warrants a compiler change, as the current state is completely usable.

> If they don't use it, their code won't get broken by the fix.

Every time we change the compiler, it may break other things. I don't think
it's worth the risk for such a small improvement. Not to mention it will bloat
all object files. Why break things for the vast majority of people when the fix
is simple for those who have been misled by the incomplete docs?

--