Andrew Kelley 656cc33f8d allow calling with a new stack to regress a bit ... Calling with a new stack, with a runtime-known stack pointer (e.g. not a global variable) is regressed with this branch. It is now a compile-error, due to the Runtime Hint system not being smart enough to mix a compile-time modifier field with a runtime stack field. I'm OK with this regression because this feature is flawed (see #3268) and may be deleted from the language.		2019-12-06 15:25:00 -05:00
..
stage1	remove @newStackCall from zig	2019-12-06 14:52:09 -05:00
stage2	exported main must be pub	2019-12-03 12:50:42 -05:00
standalone	exported main must be pub	2019-12-03 12:50:42 -05:00
assemble_and_link.zig
cli.zig
compare_output.zig	exported main must be pub	2019-12-03 12:50:42 -05:00
compile_errors.zig	allow calling with a new stack to regress a bit	2019-12-06 15:25:00 -05:00
gen_h.zig
runtime_safety.zig
stack_traces.zig
standalone.zig
tests.zig
translate_c.zig