allow code block in ** quantifiers, / foo ** { $three..$seven } /

The code block in a quantifier can either provide a range object that
is used for min and maximum quantity, or it provides a single numeric
item that is used to match exactly that many times.
bump nqp rev for dynquant implementation
Get latest MoarVM; remove nasty hack in ext ops.
Update ext ops to use new improved extop API.

Specify that many are pure, so spesh's dead code elimination can take
care of them. Also, allow a spesh function to be supplied. Implement
a basic one to toss redundant p6decontrv operations. Bump NQP_REVISION
to get a MoarVM supporting this stuff.
new extop registration interface + nqp/moar version bump
discover a bunch of facts about p6 extops for moarvm
remove debug output, discover known type of p6bool.
Hack in @a[1;2] / %h{"a";"b"} support

Attempts to change semilist directly or use a different rule were
breaking the build -- special-casing the behaviour in .[] and .{} is
much simpler than tracking down all the faulty uses of <semilist> and
making them all work with the change.
Disable an optimization on Moar that pessimizes.

What is on most backends a help gets in the way of spesh doing its
thing with multi-dispatches and inlining. For now, just don't do it
on Moar.
bump for MoarVM with inlinable lexotics
fix copy&pasto: use correct block variable in {routine,macro}_def
Tweak some protos for better Junction failover.

We can make the proto itself be (Any, Any), meaning it fails to bind.
However, this also means that the multi-dispatcher never gets chance
to sneak an entry into the cache for the Junction case, so we have to
go through the slow-path binder to fail over every time, rather than
cheaply identifying we should hit the Junction dispatcher.
Get QAST -> MAST improvemnets; follow changes.
do not try to locate a macro when we do not have a name

A ternary expression resulted if an QAST::Op(if &infix:<>) where the
ope name is ignored, but we still tried to find a macro called &infix:<>,
which is bogus.
Add a fix for RT #122423
Disallow file operations on directories

This prevents rakudo performing file operations on directories on
platforms where the OS itself does not disallow this.

This fixes RT #122358
Add new file to spectests
Merge pull request #297 from carbin/nom

Disallow file operations on directories (RT #122358)
if available, use MVM_spesh_get_and_use_facts.
Properly easter egg 42