Part of our strategy for supporting elixir is by using the mix compiler located in lumen_elixir (abstr_out branch).

The format this emits is abstract erlang (.abstr), different from the regular erlang code used by the normal frontend (.erl).

In libeir_syntax_erl there is a [separate frontend](https://github.com/eirproject/eir/blob

We need to be able to (eventually) output docs for modules (e.g. javadoc, godoc, etc). I'm fine with something like

The block comment immediately preceding the first definition of a function (or its type specification) is used as the documentation for it. The block comment immediately preceding the module declaration is used as the overall module documentation.

And maybe use markdown for f

asdf is a tool to "manage multiple runtime versions with a single CLI tool". Erlang itself and other BEAM languages (e.g. Elixir) can be installed using it and it would be very nice to add Clojure on the BEAM to the mix.

Documentation to create asdf plugins here.

Repository created [here](https://github.co

Some of the unit tests are not implemented yet.
Required someone to fill them up.

• Math functions
• List functions
• Chrono functions

Here are the incomplete unit tests (without testing the exception case).

• erlang functions

We should make better documentation about how to use the tool. I think it could be similar to talk presented on Cracows meetup (slides: https://speakerdeck.com/michalslaski/exploring-beam-based-systems-with-erlang-dot-pl) Showing possible workflow.

Generate documentation that looks somewhat better than the default edoc style (look at elixir docs).
Figure out how to publish (eg. maybe both Erlang API from xprof_core and REST API/GUI guide from xprof_gui should be copied/duplicated under xprof app documentation).
What should be the source format of non-edoc pages/guides (eg markdown)