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.

1 files changed, 2 insertions, 1 deletions

diff --git a/031address.cc b/031address.cc
index c4b260d1..79c951d0 100644
--- a/031address.cc
+++ b/031address.cc
@@ -78,7 +78,8 @@ void lookup_memory(reagent& x) {
 bool canonize_type(reagent& r) {
   while (has_property(r, "lookup")) {
     if (!r.type || r.type->value != get(Type_ordinal, "address")) {
-      raise_error << "can't lookup non-address: " << r.original_string << '\n' << end();
+      raise_error << "can't lookup non-address: " << r.to_string() << '\n' << end();
+      dump_types(r.type, cerr);  cerr << '\n';
       return false;
     }
     drop_address_from_type(r);