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:07
reportable6 left
01:10
greppable6 left,
committable6 left,
linkable6 left,
coverable6 left,
nativecallable6 left,
sourceable6 left,
bisectable6 left,
statisfiable6 left,
notable6 left,
benchable6 left,
squashable6 left,
shareable6 left,
unicodable6 left,
evalable6 left,
tellable6 left,
releasable6 left,
quotable6 left,
bloatable6 left
01:11
benchable6 joined,
squashable6 joined,
coverable6 joined,
notable6 joined
01:12
committable6 joined,
tellable6 joined,
statisfiable6 joined,
nativecallable6 joined
01:13
greppable6 joined,
shareable6 joined,
sourceable6 joined,
releasable6 joined
01:57
discord-raku-bot left
01:58
discord-raku-bot joined
02:10
reportable6 joined
02:11
bisectable6 joined
02:12
frost joined
02:13
evalable6 joined,
quotable6 joined,
linkable6 joined
02:16
sena_kun left
02:17
sena_kun joined
03:13
bloatable6 joined
03:39
frost left
04:00
discord-raku-bot left,
discord-raku-bot joined
04:13
frost joined
04:42
frost left
06:08
reportable6 left
06:10
reportable6 joined
06:11
unicodable6 joined
07:14
linkable6 left,
evalable6 left
07:17
evalable6 joined
08:05
MasterDuke left
08:17
linkable6 joined
08:43
MasterDuke joined
|
|||
MasterDuke | is it really possible to get something that can't `$foo.HOW.name($foo)`? | 09:13 | |
patrickb | nine: Then my guess of the op being reversed again was actually correct. (Not that such guesses would buy me anything but a grin :-) | 09:38 | |
nine | patrickb: definitely a good guess! | 11:22 | |
MasterDuke: just compare the output of rakudo --target=optimize -e 'my $a = 0; $a += 1;' and rakudo --target=optimize -e 'my $a = 0; $a = $a + 1;' | 11:33 | ||
MasterDuke | yeah, i saw that the += version has an extra `definite($a) ?? $a !! 0`. i wonder how possible/easy it would be to check if there's a compile-time value and if so, re-write it into the `$a = $a + 1` version (or remove that check) | 11:36 | |
nine | Worth a try I guess. | 11:38 | |
11:47
Altai-man joined
|
|||
MasterDuke | could `self.find_single_symbol('Mu', :setting-only)` in World ever actually die (i.e., not find 'Mu')? | 11:51 | |
nine | nqp::die("Cannot find symbol $name in $setting_name"); | 11:58 | |
That would indicate so | |||
Oh, 'Mu' specifically? | 11:59 | ||
lizmat | I guess very early in the bootstrap, Mu may not be a thing yet ? | 12:00 | |
nine | I dare say if we make it through settings compilation without that try, we don't need it | 12:01 | |
MasterDuke | yeah, there are a couple places where it tries to get hardcoded values, like 'Mu', and i'm wondering if those *actually* need any checks | 12:02 | |
12:07
reportable6 left
12:10
reportable6 joined
12:56
[Coke] left
12:58
Altai-man left
12:59
Altai-man joined
13:01
[Coke] joined
13:32
[Coke]_ joined
13:35
[Coke] left
14:43
tbrowder joined
15:27
MasterDuke left
15:36
MasterDuke joined
16:07
[Coke]_ is now known as [Coke]
|
|||
MasterDuke | interesting. in windows, when using an nqp with github.com/Raku/nqp/pull/764 creating even a minimal profile dies with `KnowHOW methods must be called on object instance with REPR KnowHOWREPR | 16:20 | |
at gen\moar\stage2\NQPHLL.nqp:245 (C:\Users\Dan\Source\nqp/NQPHLL.moarvm:get_remapped_type_id)` | |||
lizmat | fwiw, some of my modules currently fail testing in weird ways on Windows | 16:33 | |
[Coke] | recent failure mode? | 17:03 | |
or just-now-testing on windows? | 17:04 | ||
MasterDuke | just now testing the pr | ||
for me | |||
17:07
Altai-man left
17:12
Merfont left,
Kaiepi joined
18:06
reportable6 left
18:07
reportable6 joined
|
|||
nine | michaelheap.com/git-ignore-rev/ | 19:04 | |
lizmat | interesting | 19:06 | |
MasterDuke | yeah, just found out about that a couple months ago. good timing as we were discussing doing a repo-wide linting/formatting commit, but one of the cons was the impact on git blame. dramatically minimized that particular con | 19:07 | |
lizmat | feels there should be a trigger in a commit message to make that commit automatically be added to the ignorable commits ? | 19:08 | |
feels there should be a trigger in a commit message to make that commit automatically be added to the ignorable commits ? | 19:09 | ||
19:17
Kaiepi left,
Kaiepi joined
20:17
linkable6 left,
evalable6 left
20:19
evalable6 joined
20:51
timo joined
22:18
linkable6 joined
|
|||
Geth | MoarVM: 418711f010 | (Daniel Green)++ | src/io/syncfile.c Whoops, fix a wrong format string change It slipped in accidentally when fixing some others for MinGW. |
22:38 | |
22:46
MasterDuke left
23:41
MasterDuke joined
|