3707

Be more disciplined about tagging 2 different concepts in the codebase:

a) Use the phrase "later layers" to highlight places where a layer
doesn't have the simplest possible self-contained implementation.

b) Use the word "hook" to point out functions that exist purely to
provide waypoints for extension by future layers.

Since both these only make sense in the pre-tangled representation of
the codebase, using '//:' and '#:' comments to get them stripped out of
tangled output.

(Though '#:' comments still make it to tangled output at the moment.
Let's see if we use it enough to be worth supporting. Scenarios are
pretty unreadable in tangled output anyway.)

1 files changed, 2 insertions, 2 deletions

diff --git a/031merge.cc b/031merge.cc
index 14999123..3faee8d8 100644
--- a/031merge.cc
+++ b/031merge.cc
@@ -209,8 +209,8 @@ void check_merge_call(const vector<reagent>& ingredients, const reagent& product
   assert(false);
 }
 
-// replaced in a later layer
-// todo: find some clean way to take this call completely out of this layer
+//: replaced in a later layer
+//: todo: find some clean way to take this call completely out of this layer
 const type_tree* get_base_type(const type_tree* t) {
   return t;
 }