On 7/25/2014 2:44 PM, H. S. Teoh via Digitalmars-d wrote:
Uncommenting the const in opCmp fixes the problem. WAT?
opCmp must be const in order to be recognized for TypeInfo.
- Re: WAT: opCmp and opEqual... H. S. Teoh via Digitalmars-d
- Re: opCmp and opEquals woe... Daniel Murphy via Digitalmars-d
- Re: opCmp and opEquals... H. S. Teoh via Digitalmars-d
- Re: WAT: opCmp and opEqual... Jonathan M Davis via Digitalmars-d
- Re: WAT: opCmp and opE... Daniel Gibson via Digitalmars-d
- Re: WAT: opCmp and opE... Jonathan M Davis via Digitalmars-d
- Re: WAT: opCmp and opE... via Digitalmars-d
- Re: WAT: opCmp and opE... Jonathan M Davis via Digitalmars-d
- Re: WAT: opCmp and opE... Walter Bright via Digitalmars-d
- Re: WAT: opCmp and opE... H. S. Teoh via Digitalmars-d
- Re: WAT: opCmp and opE... Walter Bright via Digitalmars-d
- Re: WAT: opCmp and opE... Walter Bright via Digitalmars-d
- Re: WAT: opCmp and opE... H. S. Teoh via Digitalmars-d
- Re: WAT: opCmp and opE... Walter Bright via Digitalmars-d
- Re: WAT: opCmp and opE... Iain Buclaw via Digitalmars-d
- Re: WAT: opCmp and opEquals woes Walter Bright via Digitalmars-d
- Re: opCmp and opEquals woes Daniel Murphy via Digitalmars-d
- Re: opCmp and opEquals woes Jonathan M Davis via Digitalmars-d
- Re: opCmp and opEquals woe... Daniel Murphy via Digitalmars-d
- Re: opCmp and opEquals... Jonathan M Davis via Digitalmars-d
- Re: WAT: opCmp and opEquals woes Jacob Carlborg via Digitalmars-d
