03:26 apogee_ntv left 03:27 apogee_ntv joined
Geth rakudo: ugexe++ created pull request #6132:
Fix "Missing infix inside R" when using RZ/RX infix form
03:52
06:39 kjp left 06:41 kjp joined 06:42 kjp left 06:43 kjp joined 09:19 finanalyst left
Geth rakudo/main: dfaf7c8bb4 | (Nick Logan)++ (committed using GitHub Web editor) | lib/MoarVM/Profiler.rakumod
MoarVM::Profiler: use unit class to silence deprecation worry (#6131)

  `MoarVM::Profiler.rakumod` was declared as `unit module MoarVM::Profiler`
with a nested `class MoarVM::Profiler { ... }` of the same name, which triggers a deprecation worry on 6.d. Collapse the wrapper into
  `unit class MoarVM::Profiler;` with the attribute declarations at
file scope. The nested helper classes and the exported subs keep their public addresses and behavior, so external consumers are unaffected, and the file now works the same way under 6.e where the old pattern would install the class as a nested package.
10:06
rakudo/main: b7f77781be | (Elizabeth Mattijsen)++ | lib/MoarVM/Profiler.rakumod
Some additional whitespace changes

dfaf7c8bb4 fixed the warning, but left the code in a bit of a confusing whitespace state re the MoarVM::Profiler class
10:09
rakudo/main: 6e6cd5e639 | (Nick Logan)++ (committed using GitHub Web editor) | 4 files
Extend same-name-as-enclosing deprecation to cover package outers (#6130)

  * Extend same-name-as-enclosing deprecation to cover package outers
The worry added in the original deprecation commit only detected an enclosing ModuleHOW (i.e. `unit module Foo::Bar; class Foo::Bar {}`). Ecosystem modules also use `unit package Foo::Bar; role Foo::Bar {}` ... (31 more lines)
10:10
releasable6 Next release in ≈3 days and ≈7 hours. There are no known blockers. Please log your changes in the ChangeLog: github.com/rakudo/rakudo/wiki/ChangeLog-Draft 11:00
12:04 [Coke]_ joined 12:07 [Coke] left
[Coke]_ we probably want to consider 6130 for inclusion this release. 12:43
12:43 [Coke]_ is now known as [Coke][, [Coke][ is now known as [Coke]
[Coke] ... oh, it's already merged! 12:49
so much happens before I wake up. :) 12:50
14:17 kurahaupo left
disbot2 <librasteve> it’s a 24x7x365 operation 14:28
14:31 kurahaupo joined
[Coke] _I hate that expression so much - what are the units!?_ :) 14:36
Clearly created by middle management, not engineering. :) 14:37
m: say 24x365.24
evalable6 (exit code 1) ===SORRY!=== Error while compiling /tmp/KuRz_FGM2C
Confused
at /tmp/KuRz_FGM2C:1
------> say 24<HERE>x365.24
[Coke] m: say 24*365.24
evalable6 8765.76
[Coke] ... why did I expect x to work there!?
lizmat m: say "foo" x 3 14:38
evalable6 foofoofoo
lizmat m: say 24 x 3
evalable6 242424
lizmat m: say 24 x "3"
evalable6 242424
[Coke] m: say 24 x 7 x 365; 14:41
evalable6 24242424242424242424242424242424242424242424242…
[Coke], Full output: gist.github.com/683801a243448cf2ec...3b7f4693cf 14:42
[Coke] m: say [*] (24 x 7 x 365).comb
evalable6 24826572410189748758322307664430105851659752663…
[Coke], Full output: gist.github.com/84f070d42bf0357ac2...4482382ec8
lizmat m: 24 × 7 × 365
evalable6 WARNINGS for /tmp/PukjsCS13f:
Useless use of "×" in expression "× 7 × 365" in sink context (line 1)
lizmat m: say 24 × 7 × 365
evalable6 61320 14:43
lizmat m: say "×".uniname
evalable6 MULTIPLICATION SIGN