diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2015-11-07 22:26:00 -0800 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2015-11-07 22:26:00 -0800 |
commit | 562ceed016e00411407356cf6d7ec960b86811e1 (patch) | |
tree | f62835df442d47f1265e8173459997a93e4b7fae /012transform.cc | |
parent | 6fa778b3e71f625fad5e98d540b2a613328f8571 (diff) | |
download | mu-562ceed016e00411407356cf6d7ec960b86811e1.tar.gz |
2391
No, my idea was abortive. My new plan was to run no transforms for generic recipes, and instead only run them on concrete specializations as they're created. The trouble with this approach is that new contains a type specification in its ingredient which apparently needed to be transformed into an allocate before specialization. But no, how was that working? How was new computing size based on type ingredients? It might have been wrong all along.
Diffstat (limited to '012transform.cc')
-rw-r--r-- | 012transform.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/012transform.cc b/012transform.cc index b5266ed6..7837ae67 100644 --- a/012transform.cc +++ b/012transform.cc @@ -37,7 +37,7 @@ void transform_all() { recipe& r = p->second; if (r.steps.empty()) continue; if (r.transformed_until != t-1) continue; -//? cerr << " recipe " << r.name << '\n'; + // End Transform Checks (*Transform.at(t))(/*recipe_ordinal*/p->first); r.transformed_until = t; } |