03:24 apogee_ntv left 03:27 apogee_ntv joined 08:14 librasteve_ joined 08:38 sp1983_ joined 09:47 sp1983_ left 09:48 sp1983_ joined 10:43 sp1983_ left 10:52 librasteve_ left 10:53 sp1983_ joined 11:34 sp1983_ left 12:05 sp1983_ joined 12:10 sp1983_ left 12:19 sp1983_ joined 12:20 sp1983_ left
gfldex The coercion type protocol is still not documented (Rakudo release form 2021!) and I'm looking at that right now. Do I understand it right that we want to be able to use a Coercion Type at any spot where we can use a normal type and the cases where that does not apply need to be documented? 15:18
[Coke] do you mean something specific by "type protocal" as opposed to "syntax" ? 15:56
gfldex Basicly what is described in vrurg.github.io/2020/11/16/Report-...-Coercions is missing in docs.raku.org/language/typesystem#Coercion . 17:31
[Coke] Looks like the doc issue has been languishing here: github.com/Raku/doc/issues/3807 17:37
anyone see the github notes about the exposed keys? 17:38
coleman, probably: I can forward it to you if you like. probably a devops issue to resolve. 17:42
sorry, s/keys/secrets/
(although I'm guessing lizmat might be the main consumer) 17:43
coleman I will look at this 18:57
[Coke] @-mention me on the issue you're referring to? 18:58
[Coke] it's an email. 19:03
I'll forward it
coleman Someone who has admin access to the Raku/nqp repo will need to review the webhooks there. If any of those webhooks are needed, the secret needs to be rotated. github.com/Raku/infra/issues/116#i...4271614145 20:55
21:04 librasteve_ joined
timo <1 10 100 1000>.map(*.fmt("% 3s")).say; <1 10 100 1000>.map(*.fmt("% 3d")).say; 21:53
evalable6 ( 1 10 100 1000)
( 1 10 100 1000)
timo <1 10 100 1000>.map(*.fmt("% 3s")).raku.say; <1 10 100 1000>.map(*.fmt("% 3d")).raku.say;
evalable6 (" 1", " 10", "100", "1000").Seq
(" 1", " 10", " 100", " 1000").Seq
timo <1 10 100 1000>.map(*.Int.fmt("% 3s")).raku.say; <1 10 100 1000>.map(*.Int.fmt("% 3d")).raku.say; 21:54
evalable6 (" 1", " 10", "100", "1000").Seq
(" 1", " 10", " 100", " 1000").Seq
timo what do we think of this?
it feels wrong to me that the "% 3d" format gives a space in front for 2 or longer numbers 21:56