This is an example of documentation generated by ZigDoc, an alternative to Zig's built-in Auto Doc feature. See also examples in other modes/formats. The project being documented here (as the example) is the Zig standard library. Public Enum
pubconstTag = enum(u32) {
/// Tells the compiler to shut down cleanly./// No body.exit,
/// Tells the compiler to detect changes in source files and update the/// affected output compilation artifacts./// If one of the compilation artifacts is an executable that is/// running as a child process, the compiler will wait for it to exit/// before performing the update./// No body.update,
/// Tells the compiler to execute the executable as a child process./// No body.run,
/// Tells the compiler to detect changes in source files and update the/// affected output compilation artifacts./// If one of the compilation artifacts is an executable that is/// running as a child process, the compiler will perform a hot code/// swap./// No body.hot_update,
/// Ask the test runner for metadata about all the unit tests that can/// be run. Server will respond with a `test_metadata` message./// No body.query_test_metadata,
/// Ask the test runner to run a particular test./// The message body is a u32 test index.run_test,
/// Ask the test runner to start fuzzing a set of test forever or each for a given amount of/// iterations. After this is sent, the only allowed message is `new_fuzz_input`.////// The message body is:/// - a u8 test limit kind (std.Build.api.fuzz.LimitKind)/// - a u64 value whose meaning depends on FuzzLimitKind (either a limit amount or an instance id)/// - a u32 number of tests followed by n elements of/// - a u32 test name len./// - a test name with the above lengthstart_fuzzing,
/// The message body has the same format as in Server.new_fuzz_input,
/// Asks the server to run a list of steps./// Body is a `BuildSteps`./// This message only applies to the build system protocol.bsp_build_steps = 0x80000000,
_,
}