House style only uses while loops. While this has never been a formal requirement of Ramda code, I think we're pretty loathe to change it.

Usually:

var idx = -1;
while (++idx < bound) { /* ... */ }

should be hasOwnProperty not simple in

This will cause the tests to fail in old browsers, I believe.

/cc @buzzdecafe

@davidchambers Would there be problems with wrapping that test case in an if?

if (ArrayBuffer) {
    // typed array tests
}

You'd need something like this:

if (typeof ArrayBuffer !== 'undefined' && typeof Int8Array !== 'undefined') {
    // ...
}

This seems like a reasonable approach.

These assertions should either be uncommented or removed.

The idea was to leave them as reminders to attach them when we are properly able to run them: #718 (comment)

Do you have serious reservations? I would love it if we could get 0.9.0 out the door this weekend. And I think this is the only major item left.

The idea was to leave them as reminders to attach them when we are properly able to run them

I see. I had missed that comment.

Do you have serious reservations?

No.

There are merge conflicts (likely just in dist/ramda.js). I'm happy to resolve the merge conflicts and push the updated commit to master, if you like.