zig

commit 3a397795be1c0219a3a0d96082ee7d4eeddbfa7a (tree)
parent 03a7124543a52f7904090516e572b71b893c7ba2
Author: Isaac Freund <ifreund@ifreund.xyz>
Date:   Sat,  2 May 2020 23:28:44 +0200

Apply naming conventions of structs to files

Diffstat:
M
doc/langref.html.in
 | 
8
++++++++

1 file changed, 8 insertions(+), 0 deletions(-)
diff --git a/doc/langref.html.in b/doc/langref.html.in
@@ -9990,6 +9990,13 @@ coding style.
       conventions.
       </p>
       <p>
+      File names fall into two categories: types and namespaces. If the file
+      (implicity a struct) has top level fields, it should be named like any
+      other struct with fields using {#syntax#}TitleCase{#endsyntax#}. Otherwise,
+      it should use {#syntax#}snake_case{#endsyntax#}. Directory names should be
+      {#syntax#}snake_case{#endsyntax#}.
+      </p>
+      <p>
       These are general rules of thumb; if it makes sense to do something different,
       do what makes sense. For example, if there is an established convention such as
       {#syntax#}ENOENT{#endsyntax#}, follow the established convention.
@@ -9998,6 +10005,7 @@ coding style.
       {#header_open|Examples#}
       {#code_begin|syntax#}
 const namespace_name = @import("dir_name/file_name.zig");
+const TypeName = @import("dir_name/TypeName.zig");
 var global_var: i32 = undefined;
 const const_name = 42;
 const primitive_type_alias = f32;