[nem-bug] [Nemerle 0000338]: Caching in ++x macro do not play nice
with valuetypes
feedback at nemerle.org
feedback at nemerle.org
Mon May 22 18:03:35 CEST 2006
The following issue has been CLOSED
======================================================================
<http://nemerle.org/bugs/view.php?id=338>
======================================================================
Reported By: nazgul
Assigned To: malekith
======================================================================
Project: Nemerle
Issue ID: 338
Category: Compiler
Reproducibility: always
Severity: minor
Priority: high
Status: closed
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 02-12-2005 11:35 CET
Last Modified: 05-22-2006 18:03 CEST
======================================================================
Summary: Caching in ++x macro do not play nice with
valuetypes
Description:
struct S {
mutable g : int;
public play () : void {
def x = this;
x.g = 10;
++x.g;
assert (x.g == 11);
}
}
module M {
Main () : void {
def x = S();
x.play ();
}
}
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
has duplicate 0000632 Increment of fields in structs
======================================================================
----------------------------------------------------------------------
nazgul - 02-15-05 14:56
----------------------------------------------------------------------
This seems not fixable if we want to stay at parsetrees here or even with
TypedType. Maybe when we remove CExpr stage, there will be some more
useful nodes added to TExpr, so this could be fixed then.
----------------------------------------------------------------------
malekith - 05-08-06 12:00
----------------------------------------------------------------------
Reolved on trunk, as of r6245.
Issue History
Date Modified Username Field Change
======================================================================
02-12-05 11:35 nazgul New Issue
02-15-05 14:56 nazgul Note Added: 0000559
02-15-05 14:56 nazgul Status new => confirmed
02-15-05 14:56 nazgul Description Updated
02-15-05 14:56 nazgul Additional Information Updated
05-03-06 20:09 nazgul Priority normal => high
05-03-06 20:09 nazgul Description Updated
05-03-06 20:09 nazgul Additional Information Updated
05-03-06 20:11 nazgul Relationship added has duplicate 0000632
05-05-06 13:27 malekith Status confirmed => assigned
05-05-06 13:27 malekith Assigned To => malekith
05-08-06 12:00 malekith Status assigned => resolved
05-08-06 12:00 malekith Resolution open => fixed
05-08-06 12:00 malekith Note Added: 0001246
05-08-06 12:00 malekith Description Updated
05-08-06 12:00 malekith Additional Information Updated
05-22-06 18:03 nazgul Status resolved => closed
======================================================================
More information about the bugs
mailing list