[Issue 13678] TypeInfo.init is inconsistent

[via Digitalmars-d-bugs]

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

ZombineDev  changed:

   What|Removed |Added

   Keywords|preapproved |

--

[Issue 13678] TypeInfo.init is inconsistent

[via Digitalmars-d-bugs]

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

ZombineDev  changed:

   What|Removed |Added

   Keywords||preapproved
 CC||petar.p.ki...@gmail.com

--

[Issue 13678] TypeInfo.init is inconsistent

[via Digitalmars-d-bugs]

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

Steven Schveighoffer  changed:

   What|Removed |Added

 CC||schvei...@yahoo.com

--- Comment #2 from Steven Schveighoffer  ---
init.ptr is null means that the data should be initialized to zero.

As far as I know, there is no mechanism to say you shouldn't initialize the
data.

That being said, I can agree that all of the cases above should have null
pointers for init (soon to be called initializer). No reason to store those
zeros in the data segment.

--

[Issue 13678] TypeInfo.init is inconsistent

[via Digitalmars-d-bugs]

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

Mike slavo5...@yahoo.com changed:

   What|Removed |Added

 CC||slavo5...@yahoo.com

--- Comment #1 from Mike slavo5...@yahoo.com ---
https://github.com/D-Programming-Language/druntime/pull/1307 may provide a
solution to this.

--