x/clean-go-article
1
0
Fork 0
mirror of https://github.com/Pungyeon/clean-go-article.git synced 2024-11-23 06:04:05 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #46 from saireddyavs/master

Browse source 
Update README.md
This commit is contained in:
Lasse Martin Jakobsen 2023-01-31 16:24:34 +01:00 committed by GitHub
parent 5a062ef696 7e2ba16f20
commit f18fd5f884
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 12 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
README.md
View file

@ -311,7 +311,7 @@ func getReference(extension string) (string, bool) {
if !ok {
return EmptyItem, false
}
return refIface.(string)
return refIface.(string), true
}
func getItemByReference(reference string) (Item, error) {
@ -503,6 +503,7 @@ func getVal(num int) (string, error) {
if val == "" {
return NewValue() // pretend function
}
return val, err
}
func main() {
@ -832,8 +833,8 @@ func (cache *KVCache) Add(key, value string) {
This code is absolutely fine. However, the danger is that our `App` can be initialised incorrectly, without initialising the `Cache` property within. Should the following code be invoked, our application will panic:
```go
app := App{}
app.Cache.Add("panic", "now")
app := App{}
app.Cache.Add("panic", "now")
```
The `Cache` property has never been initialised and is therefore a `nil` pointer. Thus, invoking the `Add` method like we did here will cause a panic, with the following message: