Yusuke Sangenya

@gnirets Thanks, I'll concat with that solution 😄

@v0dro @lokeshh I got it. Thanks! However, I still think those behavior is confusing. Especially, when I use **Integer index**, I always have to be careful whether the argument is...

Maybe I should have proposed earlier, but another solution is creating new method that **only accepts index value**. In other words, we will have three methods `at`, `of`, and `[]`:...

> 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...

>Well I think we should return nil for indexes that don't exist (only support indexes not position)and the positions for indexes that exist as that was discussed Why `Daru::Index#[]` should...

> I believe, that's because when index is taken from variable, you can have data in one case, and just "no data" in another, and it is not an "error"....

I got it.

@aeroastro Could you please review this PR?

I have the same error as @abinashmeher999's one in my local mac osx. It seems that any other gems with native extensions doesn't have '*.so' binary file, but has '*.bundle'...