Kenn Ejima

Thanks for the PR @kshnurov, I agree with the benefits of having those features at a high level, but I'm not sure if just exposing the internal structure (which has...

> Using positions might sound more convenient in simple use cases, but these are the reasons I'm using values instead of positions: 1. I'm pretty sure most people prefer 2**38...

I'm not familiar with `insert_all` as I've been using https://github.com/zdennis/activerecord-import, but what happens if you directly pass the integer value with `user.languages.raw`?

Confirmed you can do this: ```ruby $ bin/console > profile = Profile.new => # > profile.languages = Profile.languages.keys.shuffle.take(2) => [:spanish, :english] > profile.languages.raw => 24 ``` If that's what you...

PR welcomed!

Is it compatible with the current way? If so, I would appreciate if you (or anyone else) could write up a pull request. If not, I would appreciate if you...

Can you explain why you need this feature? How and when starting with 0 is not ok? Also, do we really want to accept a start index like 2 or...

Thanks for clarifying the real use case. Based on what you described, I think a global config option would be better than a method option? Otherwise it would look: ```...

@effektz Thanks! Can you keep the test changes minimal? It's so hard to track changes.

An important design choice we have to make here is priority of existing `Hash` methods. For instance: ```ruby hashugar = Hashugar.new({merge: 1}) # if merge is treated as key =>...