#raku-dev on 18 October 2021 - Raku Programming Language Log

🦋 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: ... | log inspection situation still under development | For MoarVM see #moarvm
Set by lizmat on 22 May 2021.

00:03 reportable6 left 00:05 reportable6 joined 00:08 Kaiepi joined 00:10 Kaiepi left, Kaiepi joined 00:17 Kaiepi left, Kaiepi joined 00:26 Kaiepi left, Kaiepi joined 00:44 Kaiepi left, Kaipi joined 00:47 Kaipi left 00:48 Kaipi joined 00:51 frost joined 01:01 Kaipi left, Merfont joined 01:08 Merfont left, Merfont joined 01:42 Merfont left 01:43 Kaiepi joined 01:59 Kaiepi left, Kaiepi joined 02:20 evalable6 joined 02:33 Kaiepi left, Kaipi joined 02:36 Kaipi left 02:37 Kaiepi joined 03:09 Kaipi joined, Kaiepi left 03:16 Kaipi left 04:30 gfldex left, Voldenet left, JRaspass left, gfldex joined, JRaspass joined 04:31 Voldenet joined 05:27 Kaiepi joined 06:02 reportable6 left 06:03 reportable6 joined 07:07 Kaiepi left, Kaiepi joined 08:02 cognominal_ joined 08:03 cognominal_ joined 08:05 cog__ left 09:05 linkable6 left, evalable6 left, linkable6 joined 09:07 evalable6 joined 09:09 |Tux| joined 09:12 RakuIRCLogger left, RakuIRCLogger joined 09:44 sena_kun left

Geth

rakudo: dab7404c93 | (Elizabeth Mattijsen)++ | src/core.c/Cool.pm6
Add Cool.Version coercer

There is already a Str.Coercer. It struck me that coercing a number or a list of numbers to a Version object, would first need coercing to Str. Whereas we already do other Cool coercers. Hence this.
   say 42.Version; # v42
   say (1,2,3).Version; # v1.2.3
   say "42".match(/\d+/).Version; # v42

09:48

rakudo: 1d8bf66a5e | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | src/core.c/Cool.pm6
Merge pull request #4551 from rakudo/Cool.Version

Add Cool.Version coercer

09:53 Kaipi joined, Kaiepi left 10:04 Kaipi left 10:08 Kaiepi joined 10:38 sena_kun joined

sena_kun

releasable6, status

10:43

releasable6

sena_kun, Next release in ≈4 days and ≈8 hours. 1 blocker. Changelog for this release was not started yet

sena_kun, Details: gist.github.com/faeb26e30c1d64ac0a...e467299c36

11:05 camelia left

lizmat

m: say True.new

11:20

evalable6

False

lizmat

I understand why that returns False on a programmatical level, but on a philosophical level that feels it should either be True (as in identity) or an error

sena_kun

feels like notabug to me.

11:31

11:34 camelia joined 11:35 squashable6 left 12:02 reportable6 left 12:04 linkable6 left 12:37 squashable6 joined 12:49 linkable6 joined

timo

.o( fizzbunacci )

13:02

should Int.new also give 1 rather than 0? :P

13:03

wait i misread lol

m: say 1.new; say 2.new

camelia

0
0

sena_kun

changing this makes `new` behave like `clone`, which is a bad idea. and if we change it only for `Bool`, that's just introducing new inconsistency exception instead of having a generic rule.

13:15

13:23 frost left

lizmat

yeah, I was not going for special casing of Bool: I was more thinking that .new on an Enum should be an error

13:24

sena_kun

m: enum Foo <A B>; say A.new; say Foo::A.new; say Foo.new;

13:31

camelia

Cannot unbox a type object (Any) to a str.
in block <unit> at <tmp> line 1

sena_kun

if we should make a better error, I'd bet on this one maybe?

13:32

vrurg

Adding a throwing new to Enumeration role fixes it, except for Bool which is a special case and does do the role.

13:53

lizmat

couldn't we fix the special case as well ?

vrurg

I have $job to do right now, can't do much testing. But have an idea how to get Bool consume Enumeration.

13:57

Perhaps this would make it less of a special case.