


In Go, why can we use *os.File as parameter in bufio.NewScanner when the definition says it should only accept io.Reader?
In the Go language, when we define a function or method to receive a parameter type of io.Reader, it can actually accept any type that implements the io.Reader interface. Therefore, when we use os.File as a parameter in bufio.NewScanner, it is because the os.File type implements the io.Reader interface. This means that the os.File type can be passed as a parameter to a function or method that accepts the io.Reader type, and the io.Reader method can be used inside the function or method to operate on os.File. This flexibility is a reflection of the interface characteristics of the Go language, making the code more concise and reusable. So, even if the parameter type is declared as io.Reader, we can still use os.File as parameter passed to bufio.NewScanner.
Question content
Try to learn go and keep using bufio.newscanner
to read the file content. I use the following code to do this:
input_file, err := os.Open("input.txt") if err != nil { panic(err) } scanner := bufio.NewScanner(input_file) //do stuff
Thought I would look at the definition and see something weird (at least to me), the os.open("input.txt")
above actually returns an * os.file
and bufio.newscanner
expect a io. reader
as parameter. reader
is an interface, while file
is a struct, which doesn't implement that interface or anything like that (if that's possible).
But it looks like this is totally fine. Am I missing something about how go works? I have a c# background and it seems to me that the parameters are of different types so the compiler shouldn't allow this, right?
Just curious, don't know where else to ask this question.
Solution
os.file is actually implementing the io.reader interface.
This means that it implements all methods provided by the io.reader interface with the same signature.
In this particular case, this method:
func (f *File) Read(b []byte) (n int, err error)
The above is the detailed content of In Go, why can we use *os.File as parameter in bufio.NewScanner when the definition says it should only accept io.Reader?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



Queue threading problem in Go crawler Colly explores the problem of using the Colly crawler library in Go language, developers often encounter problems with threads and request queues. �...

The library used for floating-point number operation in Go language introduces how to ensure the accuracy is...

The problem of using RedisStream to implement message queues in Go language is using Go language and Redis...

The difference between string printing in Go language: The difference in the effect of using Println and string() functions is in Go...

What should I do if the custom structure labels in GoLand are not displayed? When using GoLand for Go language development, many developers will encounter custom structure tags...

Two ways to define structures in Go language: the difference between var and type keywords. When defining structures, Go language often sees two different ways of writing: First...

Which libraries in Go are developed by large companies or well-known open source projects? When programming in Go, developers often encounter some common needs, ...

When using sql.Open, why doesn’t the DSN report an error? In Go language, sql.Open...
