| --- | --- |
| Bugzilla Link | 349964 |
| Status | CLOSED FIXED |
| Importance | P3 normal |
| Reported | Jun 21, 2011 12:49 EDT |
| Modified | May 20, 2013 11:37 EDT |
| Version | 3.2.0 |
| Reporter | Ed Willink |
Description
The Pivot Model currently has types dependent on values and values dependent on types, but for the most part values compute their types according to the TypeManager passed in getType(...) except that tuples are harder and cache the type, so only some values are 'interchangeable' between type managers.
The CodeGen needs a lightweight evaluation type for each value, so a restructuring is desirable.
Bottom layer: StandardLibrary type system interfaces\
Next layer: Value system interfaces
Next layer: Evaluation type implementations\
Next layer: Evaluation value implementations
Or
Next layer: Pivot type implementations
Or
Next layer: Ecore type implementations
Goal: Value.getType() is a final method returning the final type field.
| --- | --- | | Bugzilla Link | 349964 | | Status | CLOSED FIXED | | Importance | P3 normal | | Reported | Jun 21, 2011 12:49 EDT | | Modified | May 20, 2013 11:37 EDT | | Version | 3.2.0 | | Reporter | Ed Willink |
Description
The Pivot Model currently has types dependent on values and values dependent on types, but for the most part values compute their types according to the TypeManager passed in getType(...) except that tuples are harder and cache the type, so only some values are 'interchangeable' between type managers.
The CodeGen needs a lightweight evaluation type for each value, so a restructuring is desirable.
Bottom layer: StandardLibrary type system interfaces\ Next layer: Value system interfaces
Next layer: Evaluation type implementations\ Next layer: Evaluation value implementations
Or
Next layer: Pivot type implementations
Or
Next layer: Ecore type implementations
Goal: Value.getType() is a final method returning the final type field.