Commit 4b898893e21fc644c4e7a163232e5e98631640d6 | zig

Apply naming conventions of structs to files

1 files changed, 8 insertions(+), 0 deletions(-)

doc/langref.html.in+8

...	...	@@ -9988,6 +9988,13 @@ coding style.
9988	9988	conventions.
9989	9989	</p>
9990	9990	<p>
	9991	File names fall into two categories: types and namespaces. If the file
	9992	(implicity a struct) has top level fields, it should be named like any
	9993	other struct with fields using {#syntax#}TitleCase{#endsyntax#}. Otherwise,
	9994	it should use {#syntax#}snake_case{#endsyntax#}. Directory names should be
	9995	{#syntax#}snake_case{#endsyntax#}.
	9996	</p>
	9997	<p>
9991	9998	These are general rules of thumb; if it makes sense to do something different,
9992	9999	do what makes sense. For example, if there is an established convention such as
9993	10000	{#syntax#}ENOENT{#endsyntax#}, follow the established convention.
...	...	@@ -9996,6 +10003,7 @@ coding style.
9996	10003	{#header_open\|Examples#}
9997	10004	{#code_begin\|syntax#}
9998	10005	const namespace_name = @import("dir_name/file_name.zig");
	10006	const TypeName = @import("dir_name/TypeName.zig");
9999	10007	var global_var: i32 = undefined;
10000	10008	const const_name = 42;
10001	10009	const primitive_type_alias = f32;