[14:51] *** MasterDuke joined
[14:53] <MasterDuke> hm. i have a change to the NQP static optimizer that changes `if @` or `if %` into `if nqp::elems`, but it dies when building NQP with `elems requires a concrete object (got a NQPMu type object instead)`, which is actually coming from the elsewhere in the static analyzer...

[14:54] <MasterDuke> https://github.com/Raku/nqp/blob/main/src/NQP/Optimizer.nqp#L71

[14:55] <MasterDuke> so i guess the generic optimization has to be `if nqp::isconcrete && nqp::elems`

[14:59] <[Coke]> and is that still a win?

[15:00] <MasterDuke> dunno, haven't done it yet

[15:01] <[Coke]> heh

[15:02] <MasterDuke> i feel like that's what the plain `if` probably ends up doing, so it might not be. the speed in lizmat's pr might be from not doing to extra check of concreteness

[15:03] <MasterDuke> so i'm trying to think of a way the optimizer can know if doing just the elems is safe

[15:08] *** MasterDuke left
[15:22] <lizmat> yeah, the difference in the PR is the concreteness check, which can be skipped for slurpy hashes

