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

Merge pull request #98 from aermolaev/patch-1

Browse source 
Update 5-interface-pollution.md: typo fixed
This commit is contained in:
Teiva Harsanyi 2024-08-13 17:06:09 +02:00 committed by GitHub
commit 22ac4b3e17
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/5-interface-pollution.md
View file

@ -47,7 +47,7 @@ Custom implementations of `io.Writer` should write the data coming from a slice
What is the rationale for having these two interfaces in the language? What is the point of creating these abstractions?
Let’s assume we need to implement a function that should copy the content of one file to another. We could create a specific function that would take as input two `*os.Files`. Or, we can choose to create a more generic function using `io.Reader` and `io.Writer` abstractions:
Let’s assume we need to implement a function that should copy the content of one file to another. We could create a specific function that would take as input two `*os.File`. Or, we can choose to create a more generic function using `io.Reader` and `io.Writer` abstractions:
```go
func copySourceToDest(source io.Reader, dest io.Writer) error {