[Issue 11108] `hasElaborateAssign` should check whether the type is assignable

Sat Oct 12 05:17:05 PDT 2013

http://d.puremagic.com/issues/show_bug.cgi?id=11108

monarchdodra at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
                 CC|                            |monarchdodra at gmail.com
         Resolution|FIXED                       |

--- Comment #5 from monarchdodra at gmail.com 2013-10-12 05:17:02 PDT ---
I don't believe this is a good choice.

I think a trait can be used inside a runtime check, and as such, all traits
should always compile.

This is currently the case for every trait we have, be they in std.traits or
std.range.

The trait name is "hasElaborateAssign". It should really just answer yes/no.
Not yes, no, error.

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