A document explaining how to use the framework efficiently needs to be created. It should be similar in spirit as the one done for gtask [http://docs.dronelabs.com/gtask]. It would be useful if the methods and types in the documentation examples linked to the API docs for said types.

No tests currently exist for the IrisTask's support for dispatching callbacks and errbacks within a main loops GMainContext. A few unit tests should be created to verify that the callback is being executed within the desired context.

it will need to:

• Create a main context
• Create a task
• Associate the context with the task using iris_task_set_main_context()
• Add a callback to the task
• Run the task
• Ensure that the callback is running from a thread owning the main loop using g_main_context_is_owner()

This should be added as a new test case in tests/task-1.c

Our iris-utils.c contains some helper methods for working with GTimeVal structs. They do not currently contain unit tests.

Unit tests should be added that create some known time vals, and compare them to verify their correctness.

Mono bindings should be created. gapi2 can be used after we register our structs properly with GLib,

Seeds seems to be doing pretty well so far, the 0.5 release works with the Gobject introspection output.

We need examples using javascript to close this issue.

We should be able to create some basic parallel constructs such as parallel for/each and sorting.

We should also think of how partitioning of the input data happens. For example, if there was an iteration interface (Like Gee.Iterable) then maybe it should get partitioned by n_threads on a scheduler.