🦋 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.
02:55 shareable6 joined, [Coke]_ joined 03:00 shareable6__ left, tellable6 left, notable6 left, quotable6 left, coverable6 left, greppable6 left, evalable6 left, bisectable6 left, [Coke] left, nebuchad` left, ilogger2 left 03:21 tellable6 joined, coverable6 joined, notable6 joined, bisectable6 joined, quotable6 joined, evalable6 joined 03:24 greppable6 joined, ilogger2 joined 03:39 zostay_ joined 03:41 SmokeMachine_ joined 03:44 zostay left, zostay_ is now known as zostay 03:48 greenfork_ joined 03:53 eof left, SmokeMachine left, greenfork left, rypervenche left, JRaspass left, greenfork_ is now known as greenfork, SmokeMachine_ is now known as SmokeMachine 03:54 rypervenche joined 03:55 eof joined 03:58 JRaspass joined 04:03 [Coke]_ is now known as [Coke] 04:08 eof left, summerisle joined 08:46 sena_kun joined
lizmat bisectable6: old=2024.04 dd Failure.new 08:53
bisectable6 lizmat, Bisecting by output (old=2024.04 new=f521883) because on both starting points the exit code is 0
lizmat, bisect log: gist.github.com/f401c830019989eb67...2e6bc51866
lizmat, (2024-05-16) github.com/rakudo/rakudo/commit/e1...295123298f
ab5tract well that's an unexpected side effect :/ 09:38
lizmat yeah, looking at it now
all those pesky little passages :-( 10:05
10:54 finanalyst joined
lizmat ab5tract: seems your last MAIN fixes also have some fallout 11:00
WARNING: unhandled Failure detected in DESTROY. If you meant to ignore it, you can mark it as handled by calling .Bool, .so, .not, or .defined methods. The Failure was:
No such symbol 'foo'
basically, any argument given generates this :( 11:01
ab5tract It shouldn’t? I wrapped the accesses in try
Will take a look when I get back to the computer
lizmat not sure what's going on here, but it's pretty annoying :-)
and left me on a wild goose chase as to how my dd changes where responsible for it :-( 11:02
ab5tract Ahh, shit. Sorry to hear that 11:03
Weird that none of the main-specific tests were failing. Anyway , I will fix it this afternoon 11:04
Geth rakudo/main: 0a0435d7f8 | (Elizabeth Mattijsen)++ | 2 files
Make dd handle Failures better

And generally make for a more pleasant experience by e.g. removing
  'Mu' from type information, and "Backtrace.new) from Failure showing
lizmat m: dd try Failure.new 11:06
camelia Nil
Geth rakudo/main: 5fbda71d7e | (Elizabeth Mattijsen)++ | src/core.c/Main.rakumod
Fix warning on each CLI argument

  ::(a) was *not* protected with a try
And some code synthetics
11:22
nqp/main: 597f46f019 | (Elizabeth Mattijsen)++ | tools/templates/MOAR_REVISION
Bump MoarVM to get MasterDuke17++ bigint ops error fixes
11:23
lizmat ab5tract: fixed the warning 11:25
noticed that the new mod nqp ops are not mentioned in github.com/Raku/nqp/blob/main/docs...down#const yet
ab5tract Ahh, thanks!
lizmat could you add them?
ab5tract Sure thing. 11:26
nine: Is M#1803 up to snuff? 11:29
linkable6 M#1803 [open]: github.com/MoarVM/MoarVM/pull/1803 Provide some mechanisms for introspecting file mode
lizmat ab5tract: it is for me, but I didn't want to mix it with MasterDuke's PR because of blin bisectability 11:30
nine is taking a look 11:31
Though I'm quite underpowered today. A week at the construction site for a friend's new house left me a bit drained. If only I had studied something useful. I hear software developer would be a quite comfy job 11:32
lizmat hehe :-)
ab5tract :)
Geth rakudo/main: 5d6a7dfcac | (Elizabeth Mattijsen)++ | tools/templates/NQP_REVISION
Bump NQP to get MasterDuke17++ bigint ops error fixes
11:33
nine Left a review 11:52
Geth rakudo/lizmat-aretype: c49797f649 | (Elizabeth Mattijsen)++ | src/core.c/Any-iterable-methods.rakumod
Introduce Any.are(type --> Bool:D)

This would allow a shorter way to say:
   sub a(@a where .are ~~ Int) { }
namely: ... (11 more lines)
11:54
rakudo: lizmat++ created pull request #5571:
Introduce Any.are(type --> Bool:D)
ab5tract nine: so that poor excuse for a pointer-y type check was only working because the ! operator was applying to the LHS, not the expression :) 12:43
but it's been gone for a little while now.
Just pushed some resolutions to your reviews. We've only got a single mode flag and while it is still set via an rw parameter, I've removed that extra function and its call and now set it in the same function that does the regular flag setup. 12:44
MasterDuke17: thanks for the review on the MoarVM PR. Somehow I didn't get pinged about them in the GH app 12:48
tellable6 ab5tract, I'll pass your message to MasterDuke
ab5tract lizmat: I really like that change to `.are` 12:55
but doesn't that where in the commit need a `*.are(Int)` or a `{ .are(Int) }` 12:56
Geth nqp/main: 51dd8b9444 | ab5tract++ | docs/ops.markdown
Document OPEN_MODE_*
13:21
16:57 vrurg left, vrurg joined
ab5tract nine: I _think_ third time is the charm :) 17:17
lizmat ab5tract: nope 17:23
sub a(@a where .are(Int)) 17:24
is enough
17:26 finanalyst left
ab5tract ok, that's a) great, b) surprising 17:26
lizmat why? 17:27
m: sub a(@a where .are ~~ Int) { dd @a ); a (1,2,3)
camelia ===SORRY!=== Error while compiling <tmp>
Missing block
at <tmp>:1
------> sub a(@a where .are ~~ Int) { dd @a ⏏); a (1,2,3)
expecting any of:
postfix
statement end
statement modifier
s…
ab5tract it's not are specific
lizmat m: sub a(@a where .are ~~ Int) { dd @a }; a (1,2,3)
camelia (1, 2, 3)
lizmat that already works ?
m: sub a(@a where .are ~~ Int) { dd @a }; a (1,2,3,"foo")
camelia Constraint type check failed in binding to parameter '@a'; expected anonymous constraint to be met but got List ((1, 2, 3, "foo"))
in sub a at <tmp> line 1
in block <unit> at <tmp> line 1
ab5tract I didn't mean that its surprising that it works for .are 17:28
I just meant I am surprised that the implicit topicalization doesn't require a block
lizmat the condition is thunked afaik
ab5tract indeed. I think its just a brain fart or something 17:37
as I have done a few where-related things in RakuAST, I must have already come across this :) 17:38
lizmat yeah you have :-)
but I know you can develop some tunnel vision when having worked on the same type of issue for a while 17:39
been there, done that :-)
ab5tract :) 17:43
20:01 MasterDuke joined 20:02 finanalyst joined 21:47 finanalyst left 22:23 sena_kun left