use for loop instead of while in SEQUENCE 

This avoids side effects:

   my @abc = ^10; my @ = @abc ... 4; say @abc;

See IRC log for this day.
using binding for better performance

There were concerns about loss of performance with for loop instead of while/shift.  A binding instead of an affectation might help.
Make flipflop smartmatch against $_ instead of calling .Bool.
remove LOLLY hack
Merge pull request #311 from bdw/nom

Add self to CREDITS
Implement IO::Handle.lines(:count)
Implement Str.lines(:count)
Implement Supply.lines
Add Supply.lines tests
Make sure lines() passes on named params
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++