Lane userdata implementation refactoring:

    - Refactor lane proxy implementation: it is now a full userdata instead
      of a table, and its methods are implemented in C instead of Lua.
      * its metatable is no longer accessible.
      * writing to the proxy raises an error.
      * it is no longer possible to overwrite its join() and cancel() methods
    - when a deep userdata idfunc requests a module to be required, manually
      check that it is not loaded before requiring it instead of relying on
      the require function's loop detection feature.
    - when a module must be required, raise an error if the 'require' function
      is not found in the target state.
    - we know Lanes is loaded in the master state, so we don't force it
      to be required in every lane too when a linda deep userdata is copied.

1 files changed, 2 insertions, 2 deletions

diff --git a/index.html b/index.html
index 9d66510..03c91f7 100644
--- a/index.html
+++ b/index.html
@@ -804,8 +804,8 @@ and for making metatables for the state-specific proxies for accessing it.
 Take a look at <tt>linda_id</tt> in <tt>lanes.c</tt>.
     </li>
     <li>Instanciate your userdata using <tt>luaG_deep_userdata()</tt>,
-        instead of the regular <tt>lua_newuserdata()</tt>.
-        Given an <tt>idfunc</tt>, it sets up the support
+    instead of the regular <tt>lua_newuserdata()</tt>.
+    Given an <tt>idfunc</tt>, it sets up the support
     structures and returns a state-specific proxy userdata for accessing your
     data. This proxy can also be copied over to other lanes.
     </li>