Started creating scripting library/namespace and added sol2 for interfacing

1 files changed, 19 insertions, 0 deletions

diff --git a/lib/sol2/docs/source/api/user.rst b/lib/sol2/docs/source/api/user.rst
new file mode 100644
index 0000000..712f2d3
--- /dev/null
+++ b/lib/sol2/docs/source/api/user.rst
@@ -0,0 +1,19 @@
+light<T>/user<T>
+================
+*utility class for the cheapest form of (light) userdata*
+
+
+.. code-block:: cpp
+	
+	template <typename T>
+	struct user;
+
+	template <typename T>
+	struct light;
+
+
+``sol::user<T>`` and ``sol::light<T>`` are two utility classes that do not participate in the full :doc:`sol::usertype\<T><usertype>` system. The goal of these classes is to provide the most minimal memory footprint and overhead for putting a single item and getting a single item out of Lua. ``sol::user<T>``, when pushed into Lua, will create a thin, unnamed metatable for that instance specifically which will be for calling its destructor. ``sol::light<T>`` specifically pushes a reference / pointer into Lua as a ``sol::type::lightuserdata``.
+
+If you feel that you do not need to have something participate in the full :doc:`usertype\<T><usertype>` system, use the utility functions ``sol::make_user( ... )`` and ``sol::make_light( ... )`` to create these types and store them into Lua. You can get them off the Lua stack / out of the Lua system by using the same retrieval techniques on ``get`` and ``operator[]`` on tables and with stack operations.
+
+Both have implicit conversion operators to ``T*`` and ``T&``, so you can set them immediately to their respective pointer and reference types if you need them.
\ No newline at end of file