Skip to content
Permalink
Browse files

Mark ops generated by METAOP_ASSIGN with the power of pod

Unfortunately, this also needed a tweak in Block.WHY to make the setting
build (the nextsame during setting building went into laland).
  • Loading branch information...
lizmat committed Nov 16, 2018
1 parent 64a47d8 commit c4445649f117aac75683effec881fc42e3d6a8a8
Showing with 2 additions and 2 deletions.
  1. +1 −1 src/core/Block.pm6
  2. +1 −1 src/core/metaops.pm6
@@ -66,7 +66,7 @@ my class Block { # declared in BOOTSTRAP

method WHY() {
if nqp::isnull($!why) {
nextsame
nextsame unless $*COMPILING_CORE_SETTING;
} else {
$!why.set_docee(self);
$!why
@@ -1,6 +1,6 @@

sub METAOP_ASSIGN(\op) {
-> Mu \a, Mu \b { a = op.( ( a.DEFINITE ?? a !! op.() ), b) }
-> Mu \a, Mu \b { a = op.( ( a.DEFINITE ?? a !! op.() ), b) } #= METAOP_ASSIGN
}

sub METAOP_TEST_ASSIGN:<//>(\lhs, $rhs) is raw { lhs // (lhs = $rhs()) }

0 comments on commit c444564

Please sign in to comment.
You can’t perform that action at this time.