From 3e836f5516c48bcfa16e0b630e53822af80d4b3b Mon Sep 17 00:00:00 2001
From: Jay Weisskopf
- The global error set should generally be avoided when possible, because it prevents - the compiler from knowing what errors are possible at compile-time. Knowing - the error set at compile-time is better for generated documentationt and for - helpful error messages such as forgetting a possible error value in a {#link|switch#}. + The global error set should generally be avoided because it prevents the + compiler from knowing what errors are possible at compile-time. Knowing + the error set at compile-time is better for generated documentation and + helpful error messages, such as forgetting a possible error value in a {#link|switch#}.
{#header_close#} {#header_close#} {#header_open|Error Union Type#}
- Most of the time you will not find yourself using an error set type. Instead,
- likely you will be using the error union type. This is when you take an error set
- and a normal type, and create an error union with the ! binary operator.
+ An error set type and normal type can be combined with the !
+ binary operator to form an error union type. You are likely to use an
+ error union type more often than an error set type by itself.
Here is a function to parse a string into a 64-bit integer: @@ -6033,4 +6033,3 @@ hljs.registerLanguage("zig", function(t) {