mw66

https://github.com/libmir/mir-ion/blob/master/source/mir/csv.d#L518 So, ndslice can have mixed types for different columns? (sorry if I miss something, I'm a newbie to mir).

> > why we may even need to provide an in-column converter callback > > The reason is simple: the ndslice's type is homogeneous, it's just double/float, but the input...

> For a scripting language it is good to have it when you need it, but if you have a type system then usually you would just tell it that...

> > Without converters in D, then how do you handle the date string in my above example? > > `mir.csv` recognise it is a timestamp. It do it for...

> > You'd better allow user to plug in his own converters for his own data. > > It is allowed now. Please check the `conversionFinalizer`. ``` conversionFinalizer : (...

It has nothing to do with Python being a scripting language. It's about the api function interface, and who (the lib or the user) is responsible for the column converters...

1) I don't understand what you mean by "that isn't generalised solution", can you elaborate? I think passing the dictionary is as general as the current `conversionFinalizer`. 2) please do...

@pontaoski can you give an example to reproduce the problem you are facing?

@pontaoski can you give example exactly what kind of problems you have? Built-in types? you mean integers/floats? They are pass-by-value semantics, hence struct, while class is pass by reference semantics.

indeed, https://github.com/ShigekiKarita/grain has some bug fix PR 5 days ago.