Grégory Horion

:+1: ! is this planned?

:+1:

Ran into the same issue, caused by npm-bcrypt being at 0.7.8_2. Fixed the issue by upgrading npm-bcrypt to latest, but then ran into [this issue on heroku](https://github.com/AdmitHub/meteor-buildpack-horse/issues/148). Downgrading to 0.8.6_1...

dup from [here](https://github.com/AdmitHub/meteor-buildpack-horse/issues/148)

hey! True, i got away with the [] and struct for map. Not sure about set, but i was wondering why and how hard would it be to implement those...

@keichi @Ericbla any update on this? :) Is this going to get merged or should we use the fork?

/test all

@SweetOps could you have a look at this one please? :)

having the same issue @haya14busa - any idea what's going on? what do you need to help debugging this? Here is what I get: ``` incsearch.vim: : function incsearch#_go[5]..177_get_input[12]..226[4]..224[1]..240[9]..239[10]..238[23]..237[22]..236[6]..209[2]..264[1]..190_call[3]..186[3]..185[17]..EasyMotion#go[3]..EasyMotion#overwin#move[1]..236_move[2]..417[1]..418[7]..421[20]..425[2]..431[26]..236_throw, line...

IMHO, API should look like this: ``` ruby h = {foo: 'bar'} Hashie::Persistable.persist(h, adapter: :json, target: 'foo.json') class Foo < Dash include Hashie::Persistable.new(persist_method: :commit) end Foo.new.commit(adapter: :json, target: 'foo.json') ```