Metabolism will be a library (either part of the standard library, optional, or a separate entity) which will hook into the compiler during compile time and allow for syntax metaprogramming. For example, stardust code can be written using metabolism to allow (<( expression )>) as a valid construct with special meaning, as well as more complex things depending on how tightly metabolism is tied to the compiler's API.
The name is a pun in the sense that a compiler 'digests' code.
Actually, I really want to avoid macro programming and generated code, as well as anything that can unexpectedly change the syntax or structure of the code.
Metabolism will be a library (either part of the standard library, optional, or a separate entity) which will hook into the compiler during compile time and allow for syntax metaprogramming. For example, stardust code can be written using metabolism to allow
(<( expression )>)
as a valid construct with special meaning, as well as more complex things depending on how tightly metabolism is tied to the compiler's API.The name is a pun in the sense that a compiler 'digests' code.