raylib

Discussion on the state of documentation for this library.

Code comments.

Using the same comments with the same style as raylib. One idea is to change them to the xmldoc style which can be used to generate external documentation. Unsure if this should be done but worth looking into.

Tech notes

Documenting api differences to make it easier for people new to raylib. Could move deta

There are a lot of examples for Raylib that can be ported to Rayfork.

This can also help with testing the library for bugs so working on this is very important.

You can make a Go image into a Raylib image, but is there any way to go back?

We should split the examples into ones that use the C API and ones that use the Python API.

We should add more examples.

We should test all the examples work, with both the static and dynamic binding.