0
Fork 0
mirror of https://codeberg.org/ziglang/zig synced 2026-11-18 07:05:05 +00:00
zig/test/cases
…
History
..
compile_errors
safety
address_of_extern_var_as_const.zig
address_space_pointer_access_chaining_pointer_to_optional_array.zig
address_spaces_pointer_access_chaining_array_pointer.zig
address_spaces_pointer_access_chaining_complex.zig
address_spaces_pointer_access_chaining_struct_pointer.zig
ambiguous_reference.zig
array_in_anon_struct.zig
blocks.zig
compile_error.zig
comptime_aggregate_print.zig
decl_value_arena.zig
dereferencing_though_multiple_pointers_with_address_spaces.zig
disable_stack_tracing.zig
error_in_nested_declaration.zig
exit.zig
export_from_body_of_coerced_fn.zig
f32_passed_to_variadic_fn.zig
f_segment_address_space_reading_and_writing.zig
float_mode_optimized_reduce.zig
fn_typeinfo_passed_to_comptime_fn.zig
for_loop.zig
function_pointers.zig
function_redeclaration.zig
global_variable_redeclaration.zig
hello_world.zig
inherit_want_safety.zig
inner_func_accessing_outer_var.zig
large_add_function.zig
large_slices.zig
maximum_sized_integer_literal.zig
nested_blocks.zig
no_compile_panic_for_unchecked_arith.zig
non_leaf_functions.zig
optionals.zig
passing_u0_to_function.zig
pic_freestanding.zig
pic_linux.zig
pie_freestanding.zig
pie_linux.zig
pointer_keeps_address_space.zig
pointer_keeps_address_space_when_taking_address_of_dereference.zig
pointer_to_explicit_generic_address_space_coerces_to_implicit_pointer.zig
print_u32s.zig
README.md
recursive_fibonacci.zig
rem.zig
returning_undefined_sentinel_terminated_const_u8_slice.zig
returns_in_try.zig
runtime_bitwise_and.zig
runtime_bitwise_or.zig
save_function_return_values_in_callee_preserved_register.zig
setting_an_address_space_on_a_local_variable.zig
simple_addition_and_subtraction.zig
simple_if_statement.zig
spirv_mergable_pointers.zig
tail_call_noreturn.zig
taking_pointer_of_global_tagged_union.zig
try_in_comptime_in_struct_in_test.zig
type_names.zig
union_unresolved_layout.zig
unused_vars.zig
while_loops.zig

Test Case Quick Reference

Use comments at the end of the file to indicate metadata about the test case. Here are examples of different kinds of tests:

Compile Error Test

If you want it to be run with zig test and match expected error messages:

// error
// is_test=true
//
// :4:13: error: 'try' outside function scope

Execution

This will do zig run on the code and expect exit code 0.

// run

Incremental Compilation

Make multiple files that have ".", and then an integer, before the ".zig" extension, like this:

hello.0.zig
hello.1.zig
hello.2.zig

Each file can be a different kind of test, such as expecting compile errors, or expecting to be run and exit(0). The test harness will use these to simulate incremental compilation.

At the time of writing there is no way to specify multiple files being changed as part of an update.

Subdirectories

Subdirectories do not have any semantic meaning but they can be used for organization since the test harness will recurse into them. The full directory path will be prepended as a prefix on the test case name.

Limiting which Backends and Targets are Tested

// run
// backend=selfhosted,llvm
// target=x86_64-linux,x86_64-macos

Possible backends are:

  • auto: the default; compiler picks the backend based on robustness.
  • selfhosted: equivalent to passing -fno-llvm -fno-lld.
  • llvm: equivalent to -fllvm.