The existing docs only contain basic usage guide for Opti(). It will be nice if more docs are provided for Opti stack, especially for to_function and options.

Not sure if this is what we need. To be clear, here is how these things SHOULD work: There should be a CMake option (looks like DOCS) that turns on generation of documentation. If that option is not set, then no docs are generated. If the option IS set, then docs will be generated. If the option is set and the required programs for generating docs do not exist (pdflatex and texi2pdf), then

For starters simple wiki with tutorials here on github should be more than enough. We should have here TSL examples in depth explanations and we should have ordinary help with screenshots explaining how to accomplish something.

In the aplication itself we could then just include help/tutorials button which would point here, to this new wiki.

tutorials and help https://github.com/PawelTroka/C

At the very least opencoarrays.F90 should be documented. Test should probably be documented as well as some build system stuff etc.

We should add some documentation (sphinx) about optional flags (compilation, cmake)
to provide details about the consequences in installation of activating/deactivating those flags

e.g. --with-fortran=OFF ==> no event driven

• Where : Install guide?
• What : all options from CMake (see cmake/default_options.cmake)

(#~#^) should be A B^T and vice versa for (#~^#). The documentation and function is above anb below the wrong type signature in each one respectively. Solution is to swap type signatures.

Wrong:

-- | Sparsifying A^T B
(#~#^) :: (MatrixRing (SpMatrix a), Epsilon a) =>
     SpMatrix a -> SpMatrix a -> SpMatrix a
a #~^# b = transpose a #~# b


-- | Sparsifying A B^T
(#~^#) :: (M

The docs are currently hosted on readthedocs here. However, this is non-ideal because one needs to do some magic in a conf.py file to do magic imports of the toolkit before reading the docstrings. A better solution is to take advantage of the fact that github hosts docs now.

We can now host the docs on clutser_toolkit.githhub.io (or somethi