| IRC logs at
Set by AlexDaniel on 12 June 2018.
00:13 sena_kun joined 00:15 Altai-man_ left 02:12 Altai-man_ joined 02:15 sena_kun left 04:13 sena_kun joined 04:15 Altai-man_ left 05:15 releasable6 left, sourceable6 left, statisfiable6 left, benchable6 left, coverable6 left, greppable6 left, bisectable6 left, linkable6 left, bloatable6 left, committable6 left, nativecallable6 left, tellable6 left, quotable6 left, notable6 left, reportable6 left, squashable6 left, shareable6 left, unicodable6 left, evalable6 left, coverable6 joined 05:16 linkable6 joined, sourceable6 joined, notable6 joined, committable6 joined, greppable6 joined, benchable6 joined 05:17 tellable6 joined, shareable6 joined, reportable6 joined, bisectable6 joined, evalable6 joined, unicodable6 joined, nativecallable6 joined 05:18 quotable6 joined, statisfiable6 joined, bloatable6 joined, squashable6 joined, releasable6 joined 05:27 Kaeipi left 05:28 Kaeipi joined 05:31 Kaeipi left, Kaeipi joined 06:05 Kaeipi left, Kaiepi joined 06:13 Altai-man_ joined 06:15 sena_kun left 08:14 sena_kun joined 08:15 Altai-man_ left 08:42 camelia left 08:51 Kaiepi left 08:52 Kaiepi joined 09:00 zakharyas joined 09:08 zakharyas left 09:10 zakharyas joined 10:13 Altai-man_ joined 10:15 sena_kun left
kawaii I don't know if here or #raku is the best place to ask for help about this, but I'm getting the following error today from one of my Perl 6 programs and I have no idea why or what it means :D 10:43
`MoarVM panic: Internal error: Unwound entire stack and missed handler`
moritz it means you've hit a bug in the rakudo + moarvm combo
kawaii it happens as a result of `return $m;` here, if that helps :)
moritz ... but I guess you knew that already :D
kawaii: that return returns out of the outer routine, not just the callback you passed to .then(). Intentional? 10:44
10:47 Altreus joined
kawaii moritz: seems that we weren't aware of that behaviour, thanks for that information :) 10:49
moritz kawaii: if you replace the 'return $m' by just '$m', you might be fine
trying to return from a routine that might have already exited might cause weird behavior (though I'd actually hope rakudo would catch such cases) 10:50
kawaii moritz: yep, seems like using just `$m;` fixed my issue there, thanks :)
moritz you're welcome 10:51
nwc10 but even the wrong code still should not panic, surely? 10:53
oh, hangon, you sort of said that with different words 10:54
moritz I tried :D 10:56
Altreus I think I got confused between P5 and Raku behaviour 11:09
I assumed that it was a real sub that gets passed to then, but I guess it's just a block
Is it always a block when you do -> { }? So return will never apply to that construct but the outer one? 11:10
moritz correct 11:20
bu fo course you write .then(sub ($p) { ... }) to ues a "full" subroutine 11:21
11:31 MasterDuke left 11:45 camelia joined 12:13 sena_kun joined 12:15 zakharyas left, Altai-man_ left 13:07 lucasb joined 14:13 Altai-man_ joined, zakharyas joined 14:15 sena_kun left
Altreus I see! I had misunderstood -> {} to be a shorthand to a sub 14:24
cos of the params you see 14:25
lizmat Altreus: you should consider the sub / method syntax as a special case of the generic block syntax, not the other way around 14:26
Altreus ah! OK :)
jnthn The type system even agrees :) 14:27
m: say Sub.^mro
camelia ((Sub) (Routine) (Block) (Code) (Any) (Mu))
Altai-man_ Altreus, don't want to be a villain, but $channel...
15:47 squashable6 left 15:50 squashable6 joined 16:08 ZzZombo left 16:13 sena_kun joined 16:15 Altai-man_ left 16:59 MasterDuke joined
Altreus for sure :) 17:42
Didn't know whether to maintain context or maintain encapsulation 17:43
The eternal dilemma
17:43 kawaii left 18:02 patrickb joined 18:12 Altai-man_ joined 18:15 sena_kun left 19:24 MasterDuke left 19:39 zakharyas left 20:13 sena_kun joined 20:15 Altai-man_ left 20:34 lucasb left, MasterDuke joined 21:19 zakharyas joined 22:06 Altai-man_ joined 22:07 zakharyas left 22:09 sena_kun left 23:20 MasterDuke left 23:37 patrickb left 23:42 MasterDuke joined