- They should share the same signatures, including parameter types and return types.
- They should share the same parameter types but can return different types.
- All functions should be the same type.
- The functions should not be a first class type.
Explanation: User defined function types in Go (Golang)
- the number of characters
- the number of bytes
- It does not accept string types.
- the number of code points
Explanation: Length of string in Go (Golang).
-
do { ... } while i < 5
-
for _,c := range "hello" { ... }
-
for i := 1; i < 5; i++ { ... }
-
for i < 5 { ... }
Explanation: Go has only for
-loops
values := []int{1, 1, 2}
-
values.append(3)
-
values.insert(3, 3)
-
append(values, 3)
-
values = append(values, 3)
Explanation: slices in GO are immutable, so calling append
does not modify the slice
const (
Write = iota
Read
Execute
)
- 0
- 1
- 2
- a random value
Reference: IOTA in Go (Golang)
-
import "github/gin-gonic/gin"
-
import "https://github.com/gin-gonic/gin"
-
import "../template"
-
import "github.com/gin-gonic/gin"
Reference: Import in GoLang
package main
var GlobalFlag string
func main() {
print("["+GlobalFlag+"]")
}
- It would not compile because
GlobalFlag
was never initialized. - It would compile and print
[]
. - It would compile and print nothing because
"[" +nil+"]"
is alsonil
. - It would compile but then panic because
GlobalFlag
was never initialized.
Explanation: most variables in Go have initial values. For string type, it's an empty string.
Here is this program on Go Playground
Q8. From where is the variable myVar
accessible if it is declared outside of any functions in a file in package myPackage
located inside module myModule
?
- It can be accessed anywhere inside
myPackage
, not the rest of myModule. - It can be accessed by any application that imports
myModule
. - It can be accessed from anywhere in
myModule
. - It can be accessed by other packages in
myModule
as long as they importmyPackage
Explanation: to make the variable available outside of myPackage
change the name to MyVar
.
See also an example of Exported names in the Tour of Go.
-
go test
-
go test -x
-
go test --verbose
-
go test -v
Reference: test package
type Point struct {
x int
y int
}
func main() {
data := []byte(`{"x":1, "y": 2}`)
var p Point
if err := json.Unmarshal(data, &p); err != nil {
fmt.Println("error: ", err)
} else {
fmt.Println(p)
}
}
- use
json.Decoder
- Pass a pointer to
data
- Make
X
andY
exported (uppercase) - Use field tags
Reference: How to Parse JSON in Golang?
Fixed version on Go Playground
- all goroutines
- any other call to lock that
Mutex
- any reads or writes of the variable it is locking
- any writes to the variable it is locking
Reference: Mutex in GoLang
Q12. What is an idiomatic way to pause execution of the current scope until an arbitrary number of goroutines have returned?
- Pass an
int
andMutex
to each and count when they return. - Loop over a
select
statement. - Sleep for a safe amount of time.
-
sync.WaitGroup
Explanation: this is exactly what sync.WaitGroup
is designed for - Use sync.WaitGroup in Golang
- It blocks the other channels.
- It is meant to be used in select statements without side effects.
- It blocks the
select
statement until the time has passed. - The goroutine does not end until the time passes.
Note: it doesn't block select
and does not block other channels.
- executing a function concurrently
- executing a different case based on the type of a variable
- executing a different case based on the value of a variable
- executing a different case based on which channel returns first
func Add(a, b int) {
return a + b
}
- A
// Calculate a + b
// - a: int
// - b: int
// - returns: int
func Add(a, b int) {
return a + b
}
- B
// Does a + b
func Add(a, b int) {
return a + b
}
- C
// Add returns the sum of a and b
func Add(a, b int) {
return a + b
}
- D
// returns the sum of a and b
func Add(a, b int) {
return a + b
}
Explanation: documentation block should start with a function name
-
myVal
must be an integer type, such asint
,int64
,int32
, etc. -
myVal
must be able to be asserted as anint
. -
myVal
must be an interface. -
myVal
must be a numeric type, such asfloat64
orint64
.
Explanation: This kind of type casting (using .(type)
) is used on interfaces only.
See this example for instance.
Primitive types are type-casted differently - Type-casting in GoLang
Example on Go Playground
- a global variable
- a medium for sending values between goroutines
- a dynamic array of values
- a lightweight thread for concurrent programming
Reference: Channels
- Check runtime.GOOS.
- Add a // +build windows comment anywhere in the file.
- Add a _ prefix to the file name.
- Add a // +build windows comment at the top of the file.
Reference: How to use conditional compilation with the go build tool, Oct 2013
data := "A group of Owls is called a parliament"
- resp, err := http.Post("https://httpbin.org/post", "text/plain", []byte(data))
- resp, err := http.Post("https://httpbin.org/post", "text/plain", data)
- resp, err := http.Post("https://httpbin.org/post", "text/plain", strings.NewReader(data))
- resp, err := http.Post("https://httpbin.org/post", "text/plain", &data)
Reference: net/http#Client.Post
Q20. What should the idiomatic name be for an interface with a single method and the signature Save() error
?
- Saveable
- SaveInterface
- ISave
- Saver
Reference: Effective Go, Interface names
- does not create; creates
- does not create; does not create
- creates; creates
- creates; does not create
Reference: Go Language Core technology (Volume one) 1.5-scope
Relevant excerpt from the article:
The second if statement is nested inside the first, so a variable declared in the first if statement is visible to the second if statement. There are similar rules in switch: Each case has its own lexical block in addition to the conditional lexical block.
- The default behavior is case insensitive, but it can be overridden.
- Fields are matched case sensitive.
- Fields are matched case insensitive.
- The default behavior is case sensitive, but it can be overridden.
Reference: encoding/json#Unmarshal
Relevant excerpt from the article:
To unmarshal JSON into a struct, Unmarshal matches incoming object keys to the keys used by Marshal (either the struct field name or its tag), preferring an exact match but also accepting a case-insensitive match. By default, object keys which don't have a corresponding struct field are ignored (see Decoder.DisallowUnknownFields for an alternative).
- Time.Add() is for performing addition while Time.Sub() is for nesting timestamps.
- Time.Add() always returns a later time while time.Sub always returns an earlier time.
- They are opposites. Time.Add(x) is the equivalent of Time.Sub(-x).
- Time.Add() accepts a Duration parameter and returns a Time while Time.Sub() accepts a Time parameter and returns a Duration.
Reference: time#Time.Add
Reference: time#Time.Sub
- Every field must have all tags to compile.
- It tightly couples different layers of your application.
- Any tags after the first are ignored.
- Missing tags panic at runtime.
Reference: Example Code / b29r0fUD1cp
- in the main function
- immediately after a line that might panic
- inside a deferred function
- at the beginning of a function that might panic
Reference: Example of Recover Function in Go (Golang)
Relevant excerpt from the article:
Recover is useful only when called inside deferred functions. Executing a call to recover inside a deferred function stops the panicking sequence by restoring normal execution and retrieves the error message passed to the panic function call. If recover is called outside the deferred function, it will not stop a panicking sequence.
- println(message)
- log.New(os.Stderr, "", 0).Println(message)
- fmt.Errorf("%s\n", message)
- fmt.Fprintln(os.Stderr, message)
- Use a proxy.
- Change the import path.
- Use a replace directive in go.mod.
- Use a replace directory.
Q28. If your current working directory is the top level of your project, which command will run all its test packages?
- go test all
- go run --all
- go test .
- go test ./...
- any, it accepts arbitary bytes
- any Unicode format
- UTF-8 or ASCII
- UTF-8
- There is no difference.
- t.Fatal does not crash the test harness, preserving output messages.
- t.Fatal stops execution of the subtest and continues with other test cases.
- t.Fatal stops all tests and contains extra information about the failed subtest.
- It raises a panic.
- It prints the log and then raises a panic.
- It prints the log and then safely exits the program.
- It exits the program.