authorgravatar for mrpaul@aestheticwisdom.comPaul <mrpaul@aestheticwisdom.com> 2020-07-11 09:09:43+07:00
committergravatar for noreply@github.comGitHub <noreply@github.com> 2020-07-11 09:09:43+07:00
log656b640e79e8cd391a046bb69713bffc3e0ff7b3
treed5b4794df1160c2ef4308688ac52b5e989fbe424
parent5afa7f2545a5f350bbac4c9d9349a7fbbd8f0977
signaturebadge-question-mark Signed by PGP key 4AEE18F83AFDEB23

Update doc/langref.html.in

Co-authored-by: Joachim Schmidt <joachim.schmidt557@outlook.com>

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

doc/langref.html.in+1-1
...@@ -312,7 +312,7 @@ pub fn main() !void {...@@ -312,7 +312,7 @@ pub fn main() !void {
312 <p>312 <p>
313 In Zig, the standard output stream's <code>print</code> function is allowed to fail because313 In Zig, the standard output stream's <code>print</code> function is allowed to fail because
314 it is actually a function defined for a generic output stream. Consider a generic output stream that314 it is actually a function defined for a generic output stream. Consider a generic output stream that
315 represents writing data to a file and the disk is full; a write to the file will fail. However,315 represents writing data to a file. When the disk is full, a write to the file will fail. However,
316 we typically do not expect writing text to the standard output stream to fail. To avoid having316 we typically do not expect writing text to the standard output stream to fail. To avoid having
317 to handle the failure case of printing to a standard output, you can use alternate functions: the317 to handle the failure case of printing to a standard output, you can use alternate functions: the
318 <code>std.log</code> function for proper logging or the <code>std.debug.print</code> function.318 <code>std.log</code> function for proper logging or the <code>std.debug.print</code> function.