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: -------
