XeLabs/100-go-mistakes
2
0
Fork 0
mirror of https://github.com/teivah/100-go-mistakes.git synced 2026-06-26 11:26:56 +08:00
Code Issues Projects Releases Packages Wiki Activity

Update 9-generics.md

Browse source 
corrected few grammar issues
This commit is contained in:
Siddharth Warrier 2023-10-14 20:49:56 +05:30 committed by GitHub
parent 668d6165fe
commit 9dbd498c8a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/9-generics.md
View file

@ -7,7 +7,7 @@ hide:
# Being confused about when to use generics
Generics is a fresh addition to the language. In a nutshell, it allows writing code with types that can be specified later and instantiated when needed. However, it can be pretty easy to be confused about when to use generics and when not to. Throughout this post, we will describe the concept of generics in Go and then delve into common use and misuses.
Generics is a fresh addition to the language. In a nutshell, it allows writing code with types that can be specified later and instantiated when needed. However, it can be pretty easy to be confused about when to use generics and when not to. Throughout this post, we will describe the concept of generics in Go and then delve into common uses and misuses.
## Concepts
@ -87,7 +87,7 @@ Restricting type arguments to match specific requirements is called a constraint
* A set of behaviors (methods)
* But also arbitrary type
Let’s see a concrete example for the latter. Imagine we don’t want to accept any `comparable` type for map key type. For instance, we would like to restrict it to either `int` or `string` types. We can define a custom constraint this way:
Let’s see a concrete example of the latter. Imagine we don’t want to accept any `comparable` type for the map key type. For instance, we would like to restrict it to either `int` or `string` types. We can define a custom constraint this way:
```go
type customConstraint interface {
@ -207,7 +207,7 @@ So when are generics useful? Let’s discuss a couple of common uses where gener
Conversely, when is it recommended **not** to use generics?
* When just calling a method of the type argument. For example, consider a function that receives an `io.Writer` and call the `Write` method:
* When just calling a method of the type argument. For example, consider a function that receives an `io.Writer` and calls the `Write` method:
```go
func foo[T io.Writer](w T) {