Touch up some comments

crates/cli-support/src/js/mod.rs

@@ -191,15 +191,11 @@ impl<'a> Context<'a> {
         // `__wbindgen_malloc`) if none of our JS glue actually needed it.
         self.unexport_unused_internal_exports();
 
-        // Handle the `start` function, if one was specified. If we're in a
+        // Initialization is just flat out tricky and not something we
-        // --test mode (such as wasm-bindgen-test-runner) then we skip this
+        // understand super well. To try to handle various issues that have come
-        // entirely. Otherwise we want to first add a start function to the
+        // up we always remove the `start` function if one is present. The JS
-        // `start` section if one is specified.
+        // bindings glue then manually calls the start function (if it was
-        //
+        // previously present).
-        // Note that once a start function is added, if any, we immediately
-        // un-start it. This is done because we require that the JS glue
-        // initializes first, so we execute wasm startup manually once the JS
-        // glue is all in place.
         let mut needs_manual_start = false;
         if self.config.emit_start {
             needs_manual_start = self.unstart_start_function();

crates/cli-support/src/lib.rs

@@ -317,6 +317,11 @@ impl Bindgen {
         // supports that aren't covered by WebIDL bindings.
         webidl::process(&mut module)?;
 
+        // Now that we've got type information from the webidl processing pass,
+        // touch up the output of rustc to insert anyref shims where necessary.
+        // This is only done if the anyref pass is enabled, which it's
+        // currently off-by-default since `anyref` is still in development in
+        // engines.
         if self.anyref {
             anyref::process(&mut module)?;
         }