aboutsummaryrefslogtreecommitdiff
path: root/exercises/082_anonymous_structs3.zig
diff options
context:
space:
mode:
authorJonathan Halmen <jonathan@halmen.org>2021-11-05 16:44:29 +0100
committerJonathan Halmen <jonathan@halmen.org>2021-11-05 17:46:56 +0100
commit88886a37d9721763326ff80a7b2c127e4a8cb8ae (patch)
tree3e6ea609c66930457907903329cdd947edafbb78 /exercises/082_anonymous_structs3.zig
parent4147a9a39b362468cc6f16c8ce751ee3481321f4 (diff)
downloadziglings-88886a37d9721763326ff80a7b2c127e4a8cb8ae.tar.gz
ziglings-88886a37d9721763326ff80a7b2c127e4a8cb8ae.tar.bz2
ziglings-88886a37d9721763326ff80a7b2c127e4a8cb8ae.tar.xz
ziglings-88886a37d9721763326ff80a7b2c127e4a8cb8ae.zip
fix whitespace line-endings
Diffstat (limited to 'exercises/082_anonymous_structs3.zig')
-rw-r--r--exercises/082_anonymous_structs3.zig2
1 files changed, 1 insertions, 1 deletions
diff --git a/exercises/082_anonymous_structs3.zig b/exercises/082_anonymous_structs3.zig
index 6b5fe04..1214589 100644
--- a/exercises/082_anonymous_structs3.zig
+++ b/exercises/082_anonymous_structs3.zig
@@ -29,7 +29,7 @@
// If a .{} thing is what the print function wants, do we need to
// break our "tuple" apart and put it in another one? No! It's
// redundant! This will print the same thing:
-//
+//
// print("{} {}\n", foo);
//
// Aha! So now we know that print() takes a "tuple". Things are