tarcieri/nio4r — comment on commit 449c36dcc39d7d159108d028b845bab4ec873317
File:  line 0
By tarcieri:

Took another stab at it here:

https://github.com/tarcieri/nio4r/commit/d8f41ceda6e2a4acaa77fddade7e3d7b25fbfddf

For whatever reason Sean's version will not pass the specs, and furthermore, the failures are identical across multiple implementations of nio4r (i.e. libev, Java NIO, pure Ruby). I'm lead to believe there's a subtle bug in the spec somewhere.

Eagerly evaluating 'subject' in the readiness example seems to resolve the issues. That's what I've checked in most recently.