The code generator in nqp for char ranges was incorrectly using ordat and
ordfirst to find the character to compare, which throw away information on
synthetic characters. We now use the getcp_s instruction instead, which leaves
synthetics negative, so that they drop out of the character range c
Test was bogus. Replaced with test that assumes Empty semantics on next.
test fixed in 06f9c5d010986a7a8dde907971e25985e8ba4601
The chance of someone using $. inside a regex and meaning what it means in Perl
5 is minimal. Best to just leave this as a "can never match".
I'm fine with the rakudo behavior here.
Rakudo now gives a decent error (X::Syntax::Signature::InvocantNotAllowed), and
there's even a test for it.