Victor Shepelev
Victor Shepelev
(Adding to milestone, needs reconsidering in a common flow of cleanup)
@Shekharrajak, I believe that: 1. Creating 1-el MultiIndex should be either impossible (error), or silently converted into just Index 2. Attempt to create MultiIndex with repeating tuples should be prohibited.
E.g.: ```ruby df = Daru::DataFrame.new({b: [11,12], a: [101,102], c: [11,22]}, order: [:a, :b, :c], index: [[:k], [:l]]) # v1: # ArgumentError: MultiIndex can't consist of single-element tuples! # or v2:...
> I think, it should allow repeating index values. I believe, index _by definition_ should be unique (it becames complicated with "category indexes" and I do not feel clearly understanding...
> "A database index is a data structure that improves the speed of data retrieval operations on a database table at the cost of additional writes and storage space to...
> I'm still struggling with understanding why indexes more complex than sequential integers are really necessary for dataframes. At least, because of "special" indexes (MultiIndex, which is easy to slice...
>What should be the output for multiple keys like `index[100,200]` ? In case one of the index is valid and the other one is not what should be the output?...
Well, I believe when first index is valid, then everything from this index to the end of Index should be returned.
> If you have any advantages of returning nil, please tell me it. Well, most of the time we a copying Ruby array's/hashes behavior. Just to be consistent. Returning `nil`...