[Issue 9186] Manifest constant can violate const correctness restrictions when empty

2012-12-21 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=9186 --- Comment #5 from monarchdo...@gmail.com 2012-12-21 01:52:11 PST --- (In reply to comment #3) > This is not a type system problem. > > All manifest constants, which declared by `enum` and T.init, make literal > expressions in the places where

[Issue 9186] Manifest constant can violate const correctness restrictions when empty

2012-12-21 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=9186 Max Samukha changed: What|Removed |Added CC||samu...@voliacable.com --- Comment #4 fr

[Issue 9186] Manifest constant can violate const correctness restrictions when empty

2012-12-21 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=9186 --- Comment #3 from Kenji Hara 2012-12-21 00:30:27 PST --- This is not a type system problem. All manifest constants, which declared by `enum` and T.init, make literal expressions in the places where they used. alias T = string[]; enum T strs

[Issue 9186] Manifest constant can violate const correctness restrictions when empty

2012-12-19 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=9186 --- Comment #2 from monarchdo...@gmail.com 2012-12-19 07:26:55 PST --- (In reply to comment #1) > (In reply to comment #0) > > The basic use case is having: > > foo(const(char)[]); > > and trying to pass a > > immutable(char)[] to it. Which is i

[Issue 9186] Manifest constant can violate const correctness restrictions when empty

2012-12-19 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=9186 Andrej Mitrovic changed: What|Removed |Added CC||andrej.mitrov...@gmail.com --- Comme