🦋 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.
06:51 camelia left 06:52 nine left 06:59 camelia joined 07:03 nine joined 07:38 sena_kun joined 07:45 sena_kun left 07:51 sena_kun joined 07:55 sena_kun left 08:24 finanalyst joined 09:03 finanalyst left 09:36 finanalyst joined
Geth rakudo/r2000: 7a682d7f9b | ab5tract++ | 2 files
Allow reduce to return containers as generated

As pointed out in R#2000 (#2000), using `reduce` on a list that includes a container was losing all knowledge of this container.
The following would previously fail: ... (19 more lines)		 09:47
linkable6 R#2000 [open]: github.com/rakudo/rakudo/issues/2000 [data types][metaop] `reduce` needlessly deconts
rakudo: ab5tract++ created pull request #5578:
Allow reduce to return containers as generated
lizmat
.oO( the most line-noisy reduce I've seen in a long time: .reduce(&[(|)]) )
 09:57
alternately, less linenoisy: .reduce(&[∪]) 09:58
ab5tract :) 10:25
a bit surprised that we don't provide secondary candidates for the "flaggy" methods in Parameter 12:49
ie, `$param.invocant(True)` 12:50
12:51 sena_kun joined
ab5tract or even more simply an `:$invocant` argument to BUILD .. maybe this is just an oversight? 13:02
Geth rakudo/add-invocant: 63d7d61510 | ab5tract++ | src/core.c/Parameter.rakumod
Add :invocant option to Parameter.new
 13:32
rakudo: ab5tract++ created pull request #5579:
Add :invocant option to Parameter.new		 13:36
rakudo/add-invocant: f1a5e878f5 | ab5tract++ | src/core.c/Parameter.rakumod
Add :invocant option to Parameter.new

Previously a user would be required to `use nqp` in order to get access to the `nqp::const::SIG_ELEM_INVOCANT` constant and manually twiddle that flags being provided to the `Parameter` constructor.
13:52 finanalyst left
Geth nqp-configure/main: d1437267ba | ab5tract++ | lib/NQP/Config.pm
Don't blow up when no reason is provided for 'not ok'
 14:02
rakudo/main: cbc4f08500 | ab5tract++ | 3rdparty/nqp-configure
Bump nqp-configure

Small fix recently added to stop it from trying to interpolate a sometimes-undefined variable if that variable happens to be undefined.		 14:59
rakudo/main: 39705b0045 | ab5tract++ | 2 files
Re-name "fixed in RakuAST" test file

Now it is clearly separated from the other tests when sorted alphabetically, which is appropriate since the tests are quite varied and are testing behaviors _changed_ by RakuAST, rather than RakuAST behavior itself.
rakudo/main: a1f98bf155 | ab5tract++ | t/12-rakuast/xx-fixed-in-rakuast.rakutest
Add test for uint parameter wrapping

In the base compiler:
  ```
   sub a(uint $a) { dd $a }
   a -1
   # -1
  ```
ab5tract putting Geth to work today :) 15:00
is R#4863 something that can (or should) be reasonably fixed in RakuAST? 15:50
linkable6 R#4863 [open]: github.com/rakudo/rakudo/issues/4863 `$a .= uc.lc` is inconsistent
ab5tract or is better addressed with a compile-time worry a la #4863? 15:54
erm, a la R#3621 15:55
linkable6 R#3621 [open]: github.com/rakudo/rakudo/issues/3621 [LTA] Emit compile-time warning for $x .= m.n
ab5tract evalable6: gist.githubusercontent.com/ab5trac...r1920.raku 16:24
evalable6 ab5tract, Successfully fetched the code from the provided URL
(signal SIGSEGV)
ab5tract damn :(
passes like a charm locally
which will make it difficult to debug... hmmm.. (R#1920) 16:25
linkable6 R#1920 [open]: github.com/rakudo/rakudo/issues/1920 [SEGV] Module loading is not thread safe
Geth rakudo/main: 13f5a74416 | ab5tract++ | t/12-rakuast/xx-fixed-in-rakuast.rakutest
Add tests for "Useless use of &... in sink context"

Or rather, the current lack-thereof of in RakuAST.
This may very well be because we haven't added the useless use worries into RakuAST at this moment, but this will make it less likely that we will overlook fixing this when we get to that point.
R#4424 (#4424)		 16:53
linkable6 R#4424 [open]: github.com/rakudo/rakudo/issues/4424 [Fixed in RakuAST] Bogus 'useless use of...in sink context'
Geth rakudo/main: b08810e418 | ab5tract++ | t/12-rakuast/xx-fixed-in-rakuast.rakutest
Fix the new tests

Someone forgot a few newlines...		 17:40
17:47 japhb left 17:49 finanalyst joined 18:24 japhb joined 18:29 Altai-man joined 18:32 sena_kun left 18:51 finanalyst left
releasable6__ Next release in ≈4 days and ≈23 hours. There are no known blockers. Please log your changes in the ChangeLog: github.com/rakudo/rakudo/wiki/ChangeLog-Draft 19:00
19:29 Altai-man left 19:30 Altai-man joined 19:33 sena_kun joined 19:34 Altai-man left
Geth rakudo/r1590: cc80e8535d | ab5tract++ | 3 files
Provide deeper context into `run` failures

After 92bd7e4, we stopped returning an exit code of `-1` for cases when attempting to `run` a nonexistent command.
This patch returns the previous behavior while also surfacing the underlying error from `libuv`, which makes it much more ... (10 more lines)		 20:32
rakudo: ab5tract++ created pull request #5580:
Provide deeper context into `run` failures		 20:33
roast: 288cd5b89a | ab5tract++ | S12-coercion/coercion-types.t
Test for no leaking BOOTStr with Str(Any)

This resolves R#1800 by testing whether a BOOTStr leaks when using a Str(Any) coercion in combination with a lookup hash.		 20:49
linkable6 R#1800 [open]: github.com/rakudo/rakudo/issues/1800 [tests needed] leaking BOOTStr
21:09 sena_kun left

Powered by Cro and the Raku® Programming Language.

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

Thank you!