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,
reportable6 joined
00:42
frost joined
01:42
committable6 left,
statisfiable6 left,
benchable6 left,
bisectable6 left,
notable6 left,
quotable6 left,
greppable6 left,
shareable6 left,
linkable6 left,
evalable6 left,
reportable6 left,
releasable6 left,
tellable6 left,
sourceable6 left,
unicodable6 left,
nativecallable6 left,
coverable6 left,
bloatable6 left
01:43
statisfiable6 joined,
benchable6 joined,
notable6 joined,
greppable6 joined,
sourceable6 joined
01:44
evalable6 joined,
coverable6 joined,
bisectable6 joined,
reportable6 joined
01:45
releasable6 joined,
tellable6 joined,
shareable6 joined,
nativecallable6 joined,
bloatable6 joined,
committable6 joined,
linkable6 joined,
quotable6 joined
01:46
unicodable6 joined
03:27
Kaiepi left
04:17
Kaiepi joined
|
|||
Nicholas | good *, * | 05:20 | |
06:07
reportable6 left
06:10
reportable6 joined
06:26
frost left
|
|||
nine | Good summer! | 07:32 | |
07:50
frost joined
|
|||
Nicholas | "while stocks last" | 07:56 | |
09:31
frost left
09:39
frost joined
12:04
frost left
12:06
reportable6 left
12:09
reportable6 joined
13:26
patrickb left
13:27
patrickb joined
14:17
discord-raku-bot left,
discord-raku-bot joined
14:28
Kaiepi left
15:34
Kaiepi joined
|
|||
lizmat | nine: re github.com/rakudo/rakudo/commit/d8ff3ade1e is that something that should be fixed on master as well ? | 16:39 | |
nine | Unless someone intends to give precompiled scripts another try, I don't see a need to rush. | 16:41 | |
If you are curious, you could test if we actually need that GLOBAL preserving in Perl6::ModuleLoader at all anymore. Since that only loads NQP modules, I don't see how Raku's GLOBAL could get overwritten | 16:42 | ||
16:51
Kaiepi left
16:56
vrurg left
|
|||
lizmat | will check | 17:02 | |
17:05
dogbert11 left
17:09
Kaiepi joined
17:26
Kaiepi left
17:48
Kaiepi joined
18:07
reportable6 left
18:08
reportable6 joined
|
|||
nine | Oooooh! find-lexical on a scope caches the negative. So my check for conflicts on IMPORT actually prevents those imported symbols from getting found | 18:48 | |
Well, it doesn't actually cache a negative. It's more that it generates the list of generated lexical declarations just the once and caches the result, preventing future additions from getting found. | 18:51 | ||
lizmat | I think I just had a record in the Rakudo code base: fixed a problem introduced in 2012, and *nobody* has noticed that until now | 19:04 | |
nine | Could be. My ModuleLoader bug was from 2013 | 19:06 | |
400! | 19:16 | ||
The 4 additional spec tests failed before because they `use Test;` twice: github.com/Raku/roast/blob/master/...-0.t#L2306 | 19:18 | ||
19:24
sena_kun left
19:25
sena_kun joined
19:34
Kaipei joined
19:37
Kaiepi left
20:34
Kaipei left
20:53
sena_kun left
20:55
sena_kun joined
21:45
Kaiepi joined
21:47
vrurg joined
21:54
vrurg left
22:03
vrurg joined
22:14
discord-raku-bot left
22:15
discord-raku-bot joined
22:16
discord-raku-bot left,
discord-raku-bot joined
|
|||
MasterDuke | os just updated to gcc 12 and there's a new warning | 22:54 | |
compiling src/jit/tile.o | |||
src/jit/tile.c: In function ‘MVM_jit_tile_make’: | |||
src/jit/tile.c:51:25: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=] | |||
51 | tile->values[i] = (MVMint8)va_arg(arglist, MVMint32); | |||
| ^ | |||
In file included from src/moar.h:286, | |||
from src/jit/tile.c:1: | |||
src/jit/tile.h:21:14: note: at offset 4 into destination object ‘values’ of size 4 | |||
21 | MVMuint8 values[4]; | |||
| ^~~~~~ | |||
drakonis | sounds like gcc added some new checkers | 23:19 | |
hot take: how long would it take to rewrite moarvm with rust | |||
Voldenet | probably depends on whether you're willing to start today ( ¬‿¬) | 23:23 | |
drakonis | its wayyyy out of my depth | 23:24 | |
japhb | drakonis: A long time. | 23:29 | |
tellable6 | 2022-05-10T20:29:09Z #raku <tonyo> japhb i understand how macros work, referring mostly to the trend of code generation vs just using macros (whether it's syntactic or semantic). go's use of code generation, in practice, is abhorrent | 23:30 | |
drakonis | it does that because it used to lack generics | 23:33 | |
it offers it now | |||
still no macros | |||
Voldenet | golang does still lack proper generics | 23:34 | |
or rather the strategy of executing generics is peculiar | |||
drakonis | it seems entirely in line with golang's modus operandi | 23:35 | |
Voldenet | and regarding rust, it probably isn't good language for this | 23:37 |