🦋 Welcome to the IRC channel of the core developers of the Raku Programming Language (raku.org #rakulang). This channel is logged for the purpose of history keeping about its development | evalbot usage: 'm: say 3;' or /msg camelia m: ... | log inspection situation still under development | For MoarVM see #moarvm
Set by lizmat on 22 May 2021.
Geth nqp: 315cc79cd8 | (Elizabeth Mattijsen)++ | tools/templates/MOAR_REVISION
Bump NQP to get the latest MoarVM fixes by nine++
 11:05
rakudo: d1bda7b56f | (Elizabeth Mattijsen)++ | tools/templates/NQP_REVISION
Bump NQP for various MoarVM and NQP fixes
 11:21
rakudo/cpucores-once: 65ddcb7c3e | (Elizabeth Mattijsen)++ | 4 files
Make sure that nqp::cpucores is only called once ever

It appears that nqp::cpucores can potentially be a heavy operation
  (even like needing to fork() apparently on MacOS Monterey), which
may well have some adverse effects.
Therefore make sure we only call nqp::cpucores only once at startup. Also introduce an implementation-detail Kernel.cpu-cores-but-one method that will be one less than the number of CPU cores, with a minimum of 1.		 11:53
lizmat (a rebase)
Geth rakudo/cpucores-once: 2113eae9f0 | (Elizabeth Mattijsen)++ | 2 files
Revert behaviour of Kernel.cpu-cores

It will now always call nqp::cpucores for those cases where the number of CPU's can actually change.
The internal method Kernel.cpu-cores-but-one is now lazy, and will only call nqp::cpucores once in the lifetime of a process.
Geth rakudo/cpucores-once: 27f8cc5788 | (Elizabeth Mattijsen)++ | 2 files
Add Kernel.cpu-cores(:cached) candidate

  - Kernel.cpu-cores now *always* calls nqp::cpucores and sets cache
  - Kernel.cpu-cores(:cached) returns cached value or makes a cached value
  - Kernel.cpu-cores-but-one always uses the cached value
  - Thread.BUILD now makes sure that Kernel.cpu-cpucores(:cached) is called
   **before** starting an OS thread		 12:12
Geth rakudo/cpucores-once: 7c10225bba | (Elizabeth Mattijsen)++ | 2 files
Kernel.cpu-cores-but-one is now the only one caching

This is also the one called by Thread.BUILD now, and the :cached candidate of Kernel.cpu-cores is gone and Kernel.cpu-cores is now back to its original state.		 13:25
ugexe regarding nqp::cpucores performance -- github.com/libuv/libuv/pull/2914#p...-451430065 suggest libuv could itself be improved 13:46
lizmat well, until then... we have a fix now 13:55
Geth rakudo/cpucores-once: 9cb2d8b5f1 | (Elizabeth Mattijsen)++ | src/core.c/Iterable.pm6
Fix erroneous but harmless use of ; vs ,
 14:10
lizmat ugexe++ for the spot
ugexe i like trailing commas because adding new things afterwards doesn't take over the blame for the original line 14:19
git blame rather
lizmat yeah, true that 14:33
pie_flavor is `eqv` the operator to check two bools for equality? 18:24
wrong channel sorry 19:25

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!