Sameer Deshmukh

I also don't think we should go for `of`. `[]` and `at` should be sufficient. I can't think of use cases where a method that accepts both index and position...

Agreed. How about `container`, or `data_store`? We'll also need to make some non-trivial changes in notebooks.

The `to_csv` indicates a Ruby class change, like `to_s` or `to_i`. You expect it return a new object, not write or read a file, hence the naming. `to_csv` will ideally...

I like @zverok 's idea. @athityakumar you should go ahead with that. Just make sure you document this properly.

I think the present functionality of `from_` should stay. It has become quite widespread due to talks/blogs/notebooks and will confuse users. The `from_*` methods can be extended to say "give...

How about `to_format.to_s` returning the `String`?

Yes. The `to_s`, `to_format` and `write_format` approach is good. The `to_s` method will return the same string that will be written to file by `write_format` right?

Just monkey patch `to_format_string` and document it nicely.

@dshvimer any update on this? Are you going to work on `io_spec`?

What use cases does this method have? Can it be made generic enough to be useful to a larger audience of data engineers?