🦋 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: ... | Logs available at irclogs.raku.org/raku-dev/live.html | For MoarVM see #moarvm
Set by lizmat on 8 June 2022.
bartolin_ c: 2018.09 role WithStub { method a() { ... } }; class C2901 does WithStub { multi method a() { "OHAI" } } 06:38
committable6 bartolin_, ¦2018.09: «4===SORRY!4=== Error while compiling /tmp/KhpOPSbAtb␤Method 'a' must be implemented by C2901 because it is required by roles: WithStub.␤at /tmp/KhpOPSbAtb:1␤ «exit code = 1»»
bartolin_ c: 2018.10 role WithStub { method a() { ... } }; class C2901 does WithStub { multi method a() { "OHAI" } }
committable6 bartolin_, ¦2018.10: «»
Geth roast: usev6++ created pull request #831:
Test implementing non-multi method stubbed in role
06:40
Xliff P6-GLib suite timing statistics for Raku 2022.12.1219.g.760.e.21.c.18 12:19
Total number of projects: 33 (502844 loc)
Total non-parallel compile times: 9018.770 (273.296 avg)
Total parallel compile times: 1694.587 (51.351 avg) 5.322x speedup
lizmat irclogs.raku.org/raku-dev/search.h...icks=Xliff 12:20
Xliff 18% increase in parallel from last week. 12:22
lizmat yeah, but if I look at the commits of last week, nothing stands out 12:24
Xliff lizmat: File locking may be a bit chaotic. 12:27
Also... environment. Although I try to keep things as free as possible when I do timings. 12:28
lizmat yeah, I wonder how much of the variation we see over the weeks, is actually noise
Xliff I would not be surprised if that is significant.
lizmat also: I still wonder if some versions of Rakudo are inherently slower than others because of a bad case of hash randomization
Xliff That's the reason I do these across the weeks. Hoping that over time the noise can be filtered out.
Hash randomization? 12:29
lizmat the ways the buckets are dealt out in a hash
Xliff Ah. 12:31
Geth roast: 1c7224ada5 | (Christian Bartolomäus)++ | S14-roles/stubs.t
Test implementing non-multi method stubbed in role

  ... as multi method in class. Compare
  github.com/Raku/old-issue-tracker/issues/2901
14:23
roast: 937a093bb4 | (Vadim Belman)++ (committed using GitHub Web editor) | S14-roles/stubs.t
Merge pull request #831 from usev6/old_issues_2901

Test implementing non-multi method stubbed in role
lizmat notable6: weekly 15:03
notable6 lizmat, 1 note: 2023-02-15T23:23:00Z <guifa_>: arstechnica.com/information-techno...nts-page=1 <-- speaking of modules ha
lizmat notable6: weekly reset 15:10
notable6 lizmat, Moved existing notes to “weekly_2023-02-20T15:10:50Z”
lizmat and yet another Rakudo Weekly News hits the Net: rakudoweekly.blog/2023/02/20/2023-...herkining/
tbrowder lizmat++ 19:46
Geth rakudo/lizmat-WARNINGS: d8e177d86b | (Elizabeth Mattijsen)++ | 2 files
Refactor significantly:

  - return "warn" sub to its previous state
  - put .WARN logic into the control exception handler (this was the
   place I was looking for earlier, it could use a different name)
  - the .WARN methods are now also expected to receive a Backtrace
   object as the second positional argument
  - this restores the capability of having a CONTROL block catching
   warnings if $*WARNINGS is something else than CX::Warn
20:03
Geth rakudo/lizmat-WARNINGS: 39e8a26416 | (Elizabeth Mattijsen)++ | src/core.c/control.pm6
Remove trailing whitespace
23:26
rakudo/main: c3b3701105 | (Elizabeth Mattijsen)++ | 2 files
Remove trailing whitespace
23:27