gaspersic/learngo
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

fix: questions typos of the if statement section

Browse Source
This commit is contained in:
Inanc Gumus
2018-10-21 23:16:30 +03:00
parent a29cb99fcb
commit 2db3731b25
7 changed files with 22 additions and 55 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
11-if/questions/4-error-handling.md
View File

@ -1,3 +1,16 @@
## Why error handling is needed?
1. I don't know.
2. To control the execution flow.
3. To make a program malware safe.
4. Because, things can go wrong. *CORRECT*
> **1:** Then, please watch the lecture again! :)
>
> **2:** Actually yes, but that's not the main reason.
>
> **3:** Come on!
## What's a nil value?
1. The dark matter that rules the universe.
2. It's a zero value for pointers or pointer-based types. It means the value is uninitialized. *CORRECT*
@ -13,25 +26,12 @@
>
## Why error handling is needed?
1. I don't know.
2. To control the execution flow.
3. To make a program malware safe.
4. Because, things can go wrong. *CORRECT*
> **1:** Then, please rewatch the lecture! :)
>
> **2:** Actually yes, but that's not the main reason.
>
> **3:** Come on!
## How Go handles error handling?
1. Using a throw/catch block
1. Using a throw/catch statement
2. Using a simple if statement with nil comparison *CORRECT*
3. Using a mechanism called tagging
> **1:** There isn't a throw/catch block in Go; unlike Java, C#, and so on... Go is explicit.
> **1:** There isn't a throw/catch statement in Go; unlike Java, C#, and so on... Go is explicit.
## When you should handle the errors?