| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 2791 | Kartik K. Agaram | 2016-03-19 | 1 | -14/+3 |
| | | | | | | | | Simplify 2790 by simply not computing any type->value inside parse_type_tree. It now only generates names, and it turns out the consumers handle the absence of values anyway. Now parse_type_tree no longer pollutes the Type_ordinal table with type ingredients. | ||||
| * | 2790 | Kartik K. Agaram | 2016-03-19 | 1 | -0/+29 |
| | | | | | | | | | The issue alluded to in the previous 2789 is now fixed. I'm not happy with my solution, though. I pollute Type_ordinal with type ingredients in parse_type_tree and simply ignore such entries later on. I'd much rather avoid the pollution in the first place, but I'm not sure how to do that.. | ||||
| * | 2778 - fix all layers | Kartik K. Agaram | 2016-03-14 | 1 | -0/+974 |