muon/CONTRIBUTING.md -rw-r--r-- 3.7 KiB
fbce5746Stone Tickle fix interp_error with no error node a day ago


Hello, thanks for considering contributing to muon. Please send patches and questions to ~lattis/muon@lists.sr.ht. Before making any big changes, please send a proposal to the mailing list so I can give you some pointers, and make sure you don't waste your time.


Muon uses a style similar to the linux kernel. A few differences are:

  • the return type of a function goes on the line above its declaration. e.g.

            return 0;
  • it still goes on the same line in a function prototype e.g.

    int main(void);
  • never omit braces for single statement if, else, for, while, etc.

  • avoid function-like macros except in exceptional cases

  • it is OK (but not great) if your line is more than 80 characters

  • please use fixed-width integer types (e.g. uint32_t, uint64_t, uint8_t) whenever possible

In general, just try to follow the style of surrounding code.


#Error handling

All errors that can be checked, should be checked. If an error is detected, an error message should be printed using interp_error, or if there is no source code associated with the error, LOG_E. The error should be immediately returned. Most functions returning a bool return false on error. The most common other type of error returning function has the return type enum iteration_result. These functions should return ir_err on error.

#Meson functions

All meson functions are defined in functions with a separate file for each object type on which the function is defined. Functions not defined on an object are in kernel.c. If the function implementation is sufficiently large, it may be broken up into a separate file under functions/<object type>/<function name>.c.

When declaring a new function, you need to add it to the "impl_tbl" at the bottom of the file. All functions should call interp_args() before they do anything, even if they don't take any arguments. interp_args takes 3 arrays, conventionally named an (args, normal), ao (args, optional), and akw (args, keyword). Any of these may be NULL. In particular, if they are all NULL then the function takes no arguments, and interp_args will ensure this is the case.

Arguments should specify what types they accept by bitwise or-ing tc_-prefixed types together. an and ao argument arrays must be terminated by an argument of type ARG_TYPE_NULL.

ARG_TYPE_GLOB can be or-d with the type of the last element of an, and will store the remaining arguments in an obj_array. This is similar to e.g. def func(a, b, *c): in python, where c is the "glob" argument.

You may also bitwise or any type with ARG_TYPE_ARRAY_OF. This "type" will cause interp_args to do the following things:

  1. coerce single elements to arrays
    • 'hello' #=> ['hello']
  2. flatten arrays
    • ['hello', [], [['world']]] #=> ['hello', 'world']
  3. typecheck all elements of the array
    • given the "type" ARG_TYPE_ARRAY_OF | obj_string, the above examples would pass, but ['a', false] would not.


The workspace is a structure that contains all the data for an entire build setup, including all subprojects, AST, options, objects, strings. Most interpreter related functions take a workspace as one of their arguments.


Meson objects are created with the make_obj function. See object.h for more information. Conventionally, all objects are referred to by id of type obj rather than a pointer.


You may be wondering, what about Garbage collection? Muon's current approach is to cleanup only once at the very end. Meson is not a Turing-complete language, so we don't need to worry about long running programs.