Don't let parens prevent "for (1..1000) { }" opt.
Avoid walking whole setting scope at startup.

This should deal with another thing that forces deserialization of all
things in the setting whether they're needed or not. Helps a little,
but probably there are further "leaks" that could be cleared up.
Implement cmp_ok() (as recently specced ;-)
Support writing to async proc STDIN also.

Includes an NQP_REVISION bump to get MoarVM improvements that enable
this.
Add missing concrete checks to avoid SEGVs.

tgt++ for reporting.
Add &lol
Have [;] and {;} return LoL-y indices for :{p,k,kv}
Bugfixes to the last commit
Fix 1[1]:exists and 1<foo>:exists
method postcircumfix:<( )> becomes method invoke

per http://irclog.perlgeek.de/perl6/2014-07-08#i_8992020
Allow old postcircumfix:<( )> to work too, for now
Uh, don't look in other classes if postcircumfix:<( )> is defined
Make sure EVAL is done in right context
Use new tests for S26
S26: Change #| to create leading declaration comments
S26: Remove leading comments from codebase

Leading comments currently break the build process (but work
otherwise), and I don't have the knowhow to fix it.  I'm
guessing it has something to do with BOOTSTRAP
Rename docs to leading_docs
Track preceding declarations
Implement trailing docs

It's pretty rudimentary at the moment, but it's a start:

  - Uses strings instead of objects
  - Only deals with package declarations
  - Doesn't deal with trailing blocks
Implement leading declarative comments for parameters