Re^9: IO::Lambda: call for participation

[xdg]

How about "conditions" instead of "predicates"? Also, at the expense of changing your API, it might be clearer if the functions names themselves were less like perl functions and more intuitively descriptive.

• read -> readable
• write -> writeable
• sleep -> timeout
• etc

My thought is that since these aren't actually executed immediately, it would be better to have names that describe the activating condition rather than names that sound like an imperative.

For documentation, I'd strongly suggest separating the perl signature from the context arguments. E.g.

read($callback) -- context stack: $filehandle, $deadline = undef