Potentially fix problem
Potentially fix problem

nine++ reported that 8ac2eecc239c1c9c7eba71becf68e8e7e4087cd4 broke
t/04-nativecall/00-misc.t , which I cannot reproduce.  However,
that commit did change the semantics slightly: instead of an Any,
a Nil would be returned for a non-existing path.  But since the
check used //= , any subsequent attemopt would run the same code
again, as //= does not differentiate between Nil and Any.

This patch does not bind to the loaded hash if the path does not
exist, effectively still having the same semantics as a non-existing
key returns nqp::null.

tony-o/rakudo,tbrowder/rakudo,MasterDuke17/rakudo,labster/rakudo,labster/rakudo,tony-o/rakudo,tony-o/rakudo,softmoth/rakudo,tbrowder/rakudo,softmoth/rakudo,tbrowder/rakudo,labster/rakudo,salortiz/rakudo,tony-o/rakudo,tony-o/rakudo,nbrown/rakudo,softmoth/rakudo,salortiz/rakudo,salortiz/rakudo,rakudo/rakudo,MasterDuke17/rakudo,labster/rakudo,nbrown/rakudo,nbrown/rakudo,tbrowder/rakudo,salortiz/rakudo,softmoth/rakudo,MasterDuke17/rakudo,tbrowder/rakudo,MasterDuke17/rakudo,rakudo/rakudo,MasterDuke17/rakudo,nbrown/rakudo,rakudo/rakudo,rakudo/rakudo,nbrown/rakudo,labster/rakudo,MasterDuke17/rakudo,salortiz/rakudo,rakudo/rakudo,labster/rakudo,tbrowder/rakudo,softmoth/rakudo,nbrown/rakudo,rakudo/rakudo,tony-o/rakudo,salortiz/rakudo