← Back to index | Original Bugzilla link

Bug 2113 – spec inconsistent with the current d1.0 behavior?

Status: RESOLVED
Resolution: INVALID
Severity: normal
Priority: P2
Component: dmd
Product: D
Version: D1 (retired)
Platform: x86
OS: Windows
Creation time: 2008-05-19T20:35:00Z
Last change time: 2014-02-24T15:30:38Z
Assigned to: bugzilla
Creator: davidl

Comments

Comment #0 by davidl — 2008-05-19T20:35:19Z

http://www.digitalmars.com/d/1.0/operatoroverloading.html The assignment operator = can be overloaded if the lvalue is a struct or class aggregate for a struct you can't have opAssign overload seems I always get the following error message: function testopassign.a.opAssign identity assignment operator overload is illegal

Comment #1 by bugzilla — 2008-06-15T23:46:26Z

Can you give an example of the code that gives you that error message?

Comment #2 by davidl — 2008-06-16T11:31:15Z

umm, i tried to overload rvalue which can be implicitly converted to the lvalue. So it's an invalid bug actually.