Skip to content

Commit

Permalink
Remove TODO
Browse files Browse the repository at this point in the history
  • Loading branch information
illicitonion committed Feb 5, 2023
1 parent 2d4cdd1 commit 23bb419
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion projects/output-and-error-handling/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,7 @@ The main reason we have these two different locations is that often times we wan

For example, imagine your program writes out a series of scores, one per line, and you were going to write those scores to a file which another program may analyse. If the output file had "Waiting for HTTP request..." or "Server error" printed in it, that would be annoying to process later on, but as a user, you my want to know why your program appears to be hanging or failing.

Another example is when something goes wrong - in your score-recording program, you may want to (reasonably) assume that anything it outputs is a number. But if something goes wrong (say, your network connection was down so the scores couldn't be fetched), reporting that on standard error means you won't accidentally try to add the error string "Network was down" to some other number. (TODO: This explanation doesn't seem very clear).
Another example is when something goes wrong - in your score-recording program, you may want to (reasonably) assume that anything it outputs is a number. But if something goes wrong (say, your network connection was down so the scores couldn't be fetched), reporting that on standard error means you won't accidentally try to add the error string "Network was down" to some other number.

#### Standard out and standard error in Go

Expand Down

0 comments on commit 23bb419

Please sign in to comment.