In a uniform column situation I would model a single Column, effectively
have:
type StringColumn struct{ Cells []string }
type FloatColumn struct{ Cells []int }
This should also make many of the operations easier to implement.
But since I'm unclear what the end goal of this solution is, I'm not sure
whether this is sufficient or whether there are better designs.
+ Egon
On Wednesday, 19 July 2017 13:48:07 UTC-7, Sofiane Cherchalli wrote:
>
> Hi!
>
> I'm a noob in Go and I need some guidance/help on this:
> https://play.golang.org/p/0TGzKiYQZn
>
> Basically I'm implementing a CSV parser, and applying transformations on
> column value.
>
> In last part of the code I'm trying to apply a function on CSVFloat type
> which satisfies Valuer interface, but I got a compiler error.
>
> In Scala language, this could be done by using map function, but how to do
> it in Golang?
>
> Thanks.
>
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
