[Issue 7477] Enum structs without specified values

2014-08-10 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=7477

Kenji Hara k.hara...@gmail.com changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #2 from Kenji Hara k.hara...@gmail.com ---
In git-head, diagnostic has been improved.

(In reply to Don from comment #0)
 struct Foo { int x; }
 enum Bar : Foo { a, b }

test.d(2): Error: cannot implicitly convert expression (0) of type int to Foo

(In reply to Jonathan M Davis from comment #1)
 The same thing happens if you do something like
 
 enum Foo : string { a, b }

test.d(1): Error: cannot implicitly convert expression (0) of type int to
string

--


[Issue 7477] Enum structs without specified values

2014-08-10 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=7477

github-bugzi...@puremagic.com changed:

   What|Removed |Added

 Resolution|WORKSFORME  |FIXED

--


[Issue 7477] Enum structs without specified values

2014-08-10 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=7477

--- Comment #3 from github-bugzi...@puremagic.com ---
Commit pushed to master at https://github.com/D-Programming-Language/dmd

https://github.com/D-Programming-Language/dmd/commit/4cf455e6c5d686aa239300f3f6e955f6e8ceac66
fix Issue 7477 - Enum structs without specified values

--


[Issue 7477] Enum structs without specified values

2012-02-09 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=7477


Jonathan M Davis jmdavisp...@gmx.com changed:

   What|Removed |Added

 CC||jmdavisp...@gmx.com


--- Comment #1 from Jonathan M Davis jmdavisp...@gmx.com 2012-02-09 14:16:33 
PST ---
The same thing happens if you do something like

enum Foo : string { a, b }

q.d(3): Error: cannot implicitly convert expression (0) of type int to string
Error: no property 'max' for type 'string'
q.d(3): Error: Integer constant expression expected instead of (__error) ==
(__error)

So, it's not really struct-specific. It affects all types which can't be
implicitly assigned 0.

It would probably be simplest to require that enums must either be values or
they must be primitive types other than arrays, or maybe outright require that
they be integral values (I question the usefulness of using bool or floating
point enums without specifying their values).

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---