placeholder docs for coroutines and finalization

website/guide/coroutines.html

@@ -0,0 +1,5 @@
+<hr> <!-- this improves readability on e.g. elinks and w3m -->
+<h2 id="coroutines">Coroutines</h2>
+
+<p>(Documentation missing.)</p>
+

website/guide/finalization.html

@@ -0,0 +1,55 @@
+<hr> <!-- this improves readability on e.g. elinks and w3m -->
+<h2 id="finalization">Finalization</h2>
+
+<p>An object which has an internal <tt>_finalizer</tt> property in
+its prototype chain is subject to finalization before being freed.
+The finalizer may be triggered by either reference counting or
+mark-and-sweep.</p>
+
+<p>The finalizer method is called with the target object as its sole
+argument.  The method may rescue the object by creating a live reference
+to the object before returning.  The return value is ignored; similarly,
+any errors thrown by the finalizer are ignored.</p>
+
+<p>Finalizers cannot currently yield.  The context executing the finalization
+can currently be any coroutine in the heap.  (This will be fixed in the future.)
+</p>
+
+<!-- FIXME: comment on whether or not finalizers are run multiple times -->
+
+<p>Example:</p>
+<pre class="ecmascript-code">
+// finalize.js
+var a;
+
+function init() {
+    a = { foo: 123 };
+
+    __duk__.setFinalizer(a, function (x) {
+        print('finalizer, foo -&gt;', x.foo);
+    });
+}
+
+// create object, reference it through 'a'
+init();
+
+// delete reference, refcount triggers finalization immediately
+print('refcount finalizer');
+a = null;
+
+// mark-and-sweep finalizing happens here (at the latest) if
+// refcounting is disabled
+print('mark-and-sweep finalizer')
+__duk__.gc();
+</pre>
+
+<p>If you run this with the Duktape command line tool (with the default
+Duktape profile), you'll get:</p>
+<pre>
+$ duk finalize.js
+refcount finalizer
+finalizer, foo -&gt; 123
+mark-and-sweep finalizer
+Cleaning up...
+</pre>
+