[Nemerle 0000979]: yielding: don't always transform var->field

0 views
Skip to first unread message

feed...@nemerle.org

unread,
Dec 9, 2008, 5:36:21 PM12/9/08
to nemerl...@googlegroups.com

The following issue has been UPDATED.
======================================================================
<http://nemerle.org/bugs/view.php?id=979>
======================================================================
Reported By: divan
Assigned To:
======================================================================
Project: Nemerle
Issue ID: 979
Category: Compiler
Reproducibility: always
Severity: feature
Priority: low
Status: new
======================================================================
Date Submitted: 03-23-2007 20:54 CET
Last Modified: 12-09-2008 23:36 CET
======================================================================
Summary: yielding: don't always transform var->field
Description:
Redundant fields use cpu&ram, and create some restrictions.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0001072 Allow try inside expressions
======================================================================

----------------------------------------------------------------------
divan - 12-09-08 23:36
----------------------------------------------------------------------
Now it compiles, priority is lowered.

Issue History
Date Modified Username Field Change
======================================================================
03-23-07 20:54 divan New Issue
04-22-07 13:14 divan Issue Monitored: divan
12-30-07 12:11 divan Relationship added related to 0001072
12-09-08 23:36 divan Note Added: 0002147
12-09-08 23:36 divan Priority normal => low
12-09-08 23:36 divan Summary yielding: don't always
transform var->field => yielding: don\'t always transform var->field
12-09-08 23:36 divan Additional Information Updated
======================================================================

Reply all
Reply to author
Forward
0 new messages