Sameer Deshmukh

@mohawkjohn why even keep this function if `#inverse` can very well calculate inverses for 3x3 matrices?

Or maybe even use [libcsv](http://sourceforge.net/projects/libcsv/).

I'd prefer libcsv. No point in reinventing the wheel. Keep in mind that there should be no conversion to Ruby data types after the CSV has been read. Everything should...

Have a look at this: https://github.com/wiseio/paratext I think its the fastest CSV reader around and having a wrapper over that would be awesome :dancing_women:

I would like to work on this one next... Could you assign me to it please? Could you also enlist a few pointers to get me started on it? That...

I will immediately start my research on this issue, from the pointers that you have provided. Currently I have a vague idea on opaque struct pointers, I will go through...

What I've found out about opaque types so far is that they are nothing but `struct`'s which have been declared but not necessarily defined. You can change the underlying implementation...

I think the declarations for the types can go into `types.h`?

Another question: What should the new structs be named? What I think is, for scenarios where the data type indicates the actual data inside a matrix, for example `void* elements`...

If you're on Mac you should clang not gcc. https://github.com/SciRuby/nmatrix/issues/584