Make sure we return Int's with .signal()
Remove premature optimization

$*KERNEL.signal has all the mapping we need
Add Proc::Async.kill tests back again

They shouldn't hang anymore
bump nqp rev for moar with C global support
Normalize (chars|bytes)_supply handling

Step #1 in ensuring the order in which we "more" values.
Apply ordering logic, same as with Proc::Async
.words also Cool, like .lines, pass any parameters
Code esthetics

Make all .lines methods use same sane variable scheme and use fewer
calculations.
Make Str.words lazy and according to spec

The spec does *not* mention that the first word should be returned instead of
the list, if there is only one word found.  This causes a problem with << >>
interpolation at the moment, which is under investigation.

Also add add :eager / :count parameters.  The :eager version is about 10%
faster than before.  The :count version is about 30% faster than the
equivalent (:eager).elems.
Fix problem with << >> interpolation, FROGGS++
Prevent minor issues Str.lines
Re-instate a better single-arg push, plus tweaks.

With this, we re-gain the lost performance on the perl6-bench push
benchmarks, and actually do better than before the regression. Also,
the benchmark the single arg candidate was removed for now also runs
faster with it back in place (around 15% less time).
Further optimizations of push.

This cuts the perl6-bench while_push benchmark in half again, and
provides a further small improvement for the push/split benchmark.
Implement Supply.words, according to spec
Add Supply.words tests to spectest
Some initial ChangeLog entries for 2014.10
Implement IO::Handle.words
use nqp::readcharsfh on Moar, fix some logic issues
Make $limit always imply eager
Mention IO::Handle.words