These are chat archives for opal/opal

Jan 2017
Adam Jahn
Jan 31 2017 21:21

Would anyone be so kind as to provide some info on why the Native module's Hash initializer requires the native object to have a constructor of Object? Source:

I'm currently wrapping a library that has tons of objects created via Object.create(null), which means even though they essentially are behaving as an options hash, I can't simply wrap them in'opts').

As a work around, I'm simply setting opts.constructor = Object before'opts'), but I don't like it.