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

fix: wordings in go type system/questions

Browse Source
This commit is contained in:
Inanc Gumus
2018-11-09 13:34:51 +03:00
parent 28d27c9e02
commit 9b4dce0e87
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
09-go-type-system/questions/01-questions-predeclared-types.md
View File

@ -37,7 +37,7 @@
## What's the output of following code?
```go
fmt.Printf("%08b = %d", 2)
fmt.Printf("%08b = %d", 2, 2)
```
1. 00000001
2. 00000010 *CORRECT*

6
09-go-type-system/questions/02-questions-defined-types.md
View File

@ -8,7 +8,7 @@
>
## Let's suppose that you've declared the following defined type. Which property below that the new type doesn't get from its underlying type?
## Let's suppose that you've declared the following defined type. Which property below the new type doesn't get from its underlying type?
```go
// For example, let's say that you've defined a new type
@ -102,9 +102,9 @@ type (
> **1:** That's right. Go's type system is flat. So, the defined type's underlying type is a type with a real structure. int64 is not just a name, it has its own structure, it's a predeclared type.
>
> **2:** Duration is just a new type name. It doesn't its own structure.
> **2:** Duration is just a new type name. It doesn't have its own structure.
>
> **3:** Century is just a new type name. It doesn't its own structure.
> **3:** Century is just a new type name. It doesn't have its own structure.
>