2403 - experiment: documenting non-assertions

Is that like a Maybe type in a type system? No it's more, it captures
the wistful longing of several hours spent trying to make an assertion
true. Not even by moving my phases relating to the types around could I
make this assertion true.

2 files changed, 2 insertions, 2 deletions

diff --git a/030container.cc b/030container.cc
index 186d6929..94310855 100644
--- a/030container.cc
+++ b/030container.cc
@@ -535,8 +535,8 @@ void check_or_set_invalid_types(const recipe_ordinal r) {
 }
 
 void check_or_set_invalid_types(type_tree* type, const string_tree* type_name, const string& block, const string& name) {
+  // can't assert that type_name is non-null, even at the top of a recursive call tree
   if (!type) return;  // will throw a more precise error elsewhere
-//?   cerr << "checking ";  dump_types(type, cerr);  cerr << '\n';
   // End Container Type Checks
   if (type->value == 0) {
     assert(!type->left && !type->right);
diff --git a/048check_type_by_name.cc b/048check_type_by_name.cc
index fff48395..093b7d09 100644
--- a/048check_type_by_name.cc
+++ b/048check_type_by_name.cc
@@ -14,7 +14,7 @@ recipe main [
 ]
 +error: main: x used with multiple types
 
-:(after "Transform.push_back(check_or_set_invalid_types)")
+:(before "Transform.push_back(check_or_set_invalid_types)")
 Transform.push_back(check_types_by_name);  // idempotent
 
 :(code)