|
Welcome to the main channel on the development of MoarVM, a virtual machine for NQP and Rakudo (moarvm.org). This channel is being logged for historical purposes. Set by lizmat on 24 May 2021. |
|||
|
00:08
reportable6 left
00:10
reportable6 joined
00:54
frost joined
01:50
frost left
02:36
MasterDuke left
03:40
quotable6 left,
evalable6 left,
bisectable6 left,
reportable6 left,
linkable6 left,
benchable6 left,
releasable6 left,
sourceable6 left,
shareable6 left,
bloatable6 left,
unicodable6 left,
greppable6 left,
coverable6 left,
statisfiable6 left,
tellable6 left,
squashable6 left,
committable6 left,
nativecallable6 left,
notable6 left
03:41
bisectable6 joined
03:42
reportable6 joined,
bloatable6 joined
03:43
committable6 joined,
releasable6 joined,
statisfiable6 joined
04:41
sourceable6 joined
04:42
unicodable6 joined,
squashable6 joined,
coverable6 joined
04:43
benchable6 joined,
notable6 joined,
nativecallable6 joined,
quotable6 joined
05:43
sourceable6 left,
benchable6 left,
squashable6 left,
coverable6 left,
committable6 left,
nativecallable6 left,
quotable6 left,
releasable6 left,
bloatable6 left,
bisectable6 left,
unicodable6 left,
statisfiable6 left,
reportable6 left,
notable6 left
05:44
evalable6 joined,
unicodable6 joined,
nativecallable6 joined,
reportable6 joined
05:45
squashable6 joined
05:46
releasable6 joined,
committable6 joined,
bloatable6 joined
05:47
coverable6 joined
06:09
reportable6 left
06:45
quotable6 joined,
notable6 joined
|
|||
| Nicholas | good *able6, #moarvm | 06:52 | |
|
07:11
reportable6 joined
07:44
statisfiable6 joined
07:47
bisectable6 joined
08:47
TheAthlete joined
|
|||
| lizmat | good *, Nicholas | 09:12 | |
| m: dd :(UInt:D $a) # I guess that still needs to be fixed ? | |||
| camelia | :(Int:D $a where { ... }) | ||
|
09:41
tellable6 joined
09:42
linkable6 joined
09:44
sourceable6 joined
09:46
benchable6 joined
10:26
TheAthlete left
10:42
shareable6 joined,
greppable6 joined
|
|||
| jnthnwrthngtn | moarning o/ | 10:49 | |
| Nicholas | \p | ||
| oops, off by one | |||
| \o | |||
| lizmat is unclear on the state of nine's unsigned int work | 10:50 | ||
| is it correct to say that it all got merged ? | |||
| Nicholas | I don't know. I thought yes. But I don't know. And I don't know what other "fallout" there is, and what needs doing | 10:52 | |
| lizmat | ok, but the bulk of the work got merged... I know there's some fallout, which is why there won't be a 2022.01 release | 10:53 | |
| m: sub a(uint $a) { dd $a }; a -42 # that feels unexpected to me | 11:11 | ||
| camelia | -42 | ||
| lizmat | a. that it dispatches without bind failure | ||
| b. even if it did dispatch, that inside the sub the unsigned int has a negative value | |||
|
11:37
Altai-man joined
|
|||
| nine | It's all merged, yes | 11:57 | |
| MoarVM is still somewhat lenient. I figured lets take it one explosion at a time | 11:58 | ||
| In my defence its not just uint regressions that defied having a 2022.01 release | 11:59 | ||
|
12:08
reportable6 left
12:09
reportable6 joined
12:10
frost joined
|
|||
| lizmat | And yet another Rakudo Weekly News hits the Net: rakudoweekly.blog/2022/01/24/2022-...ned-merge/ | 12:20 | |
| ok, this gets a bit weird: | 12:36 | ||
| m: sub a(uint $a) { dd $a.Str }; a -42 # feels correct | 12:37 | ||
| camelia | "18446744073709551574" | ||
| lizmat | m: sub a(uint $a) { say $a.gist }; a -42 | ||
| camelia | 18446744073709551574 | ||
| lizmat | also feels correct | ||
| m: sub a(uint $a) { say $a.raku }; a -42 # ok! | 12:38 | ||
| camelia | 18446744073709551574 | ||
| lizmat | m: sub a(uint $a) { say $a }; a -42 # huh ? | ||
| camelia | -42 | ||
| lizmat | fwiw, I think the binding is correct: natives specifically don't need to check for overflow or underflow, right ? | 12:39 | |
| m: sub a(uint $a) { $a.say }; a -42 # the problematic case I think | 12:40 | ||
| camelia | -42 | ||
| nine | Could be that for so.e methods we have int candidates but no uint candidates and we coerce the uint to int to make it fit | 12:45 | |
| And yes natives are a performance tool foremost, so overflow/underflow is explicitely allowed | 12:46 | ||
|
12:50
frost left
13:03
frost joined,
TheAthlete joined
13:52
discord-raku-bot left
13:53
discord-raku-bot joined
14:09
frost left
14:12
frost joined
|
|||
| [Coke] | nine++ again, btw. | 14:27 | |
|
15:32
frost left
16:37
sena_kun_ joined,
Altai-man left
|
|||
| moon-child | m: m: sub a(uint $a) { say +$a }; a -42 | 17:46 | |
| camelia | -42 | ||
|
17:56
Altai-man joined
17:58
sena_kun_ left
18:06
reportable6 left,
reportable6 joined
18:26
Altai-man left
|
|||
| [Coke] | in an ideal world, would that accept the arg, get the correspond int you'd expect from a shift in C and return that? Or would it error out? | 19:17 | |
| moon-child | I would expect an error, as -42 can not be converted to uint. However I would expect wrapping from, say, my uint $x = 14; $x = -$x | 19:25 | |
| lizmat | mL sub a(uint $a) { say $a.Str }; a -42 | 19:33 | |
| m: sub a(uint $a) { say $a.Str }; a -42 | |||
| camelia | 18446744073709551574 | ||
| lizmat | the problem is in uint.say really | ||
| going afk to record a presentation | |||
| well, offline actually :-) | |||
|
19:34
lizmat left
20:31
lizmat joined
|
|||
| lizmat | mission accomplished and uploaded :-) | 20:38 | |
|
20:46
TheAthlete left
22:02
MasterDuke joined
23:24
sena_kun left
23:50
sena_kun joined
|
|||