Accept functions as interfaces about go-linq

[ahmetb]

@bsideup hmm, I am not sure I understood what's going on from the code. Can you please elaborate?

[bsideup]

@ahmetalpbalkan yes, I will try :)

Currently what we have in Go-linq:

We receive func with T (aka interface{}) signature, then users almost always perform casting:

over18Names, err := From(students)
    .Where(func (s T) (bool,error){
        return s.(*Student).age >= 18, nil
    })
    .Select(func (s T) (T,error){
        return s.(*Student).name, nil
    }).Results()

But, since casting is a must, we can move it into the go-linq and allow users to specify type on func's signature, so this code will look like this:

over18Names, err := From(students)
    .Where(func (s Student) (bool,error){
        return s.age >= 18, nil
    })
    .Select(func (s Student) (T,error){
        return s.name, nil
    }).Results()

Technically it's possible with reflection. I you want I can implement it and send as a pull request :)

[ahmetb]

@bsideup ooh interesting. What would be the method signatures for Where/Select in this case?

[ahmetb]

@bsideup If you're still interested, I'd love to see a prototype. It appears like this would make these methods accept interface{} rather than []linq.T. I have a feeling like this would make the caller code cleaner although it'll probably make it a bit harder to use for the first time, but then we have errors etc to handle that. Feel free to send something over to discuss if you like.

[bsideup]

@ahmetalpbalkan sorry for no response for a long time, was busy a little bit

actually, I did some research, and it looks like reflection will affect performance :(

Also, I found this great post about it:
http://blog.burntsushi.net/type-parametric-functions-golang/