|
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:00
rypervenche left,
jgaz left,
reportable6 left,
jgaz joined,
rypervenche joined,
rypervenche left,
rypervenche joined
00:03
reportable6 joined
00:24
jgaz left,
jgaz joined
|
|||
| MasterDuke | brrt++ | 01:35 | |
|
01:50
MasterDuke left
02:55
camelia left
02:59
camelia joined
04:46
unicodable6 left,
sourceable6 left,
greppable6 left,
committable6 left,
notable6 left,
squashable6 left,
notable6 joined
04:47
committable6 joined
04:48
unicodable6 joined,
greppable6 joined,
sourceable6 joined,
squashable6 joined
05:48
quotable6 left,
benchable6 left,
linkable6 left,
tellable6 left,
bisectable6 left,
releasable6 left,
evalable6 left,
greppable6 left,
statisfiable6 left,
shareable6 left,
bloatable6 left,
unicodable6 left,
coverable6 left,
committable6 left,
squashable6 left,
reportable6 left,
nativecallable6 left,
notable6 left
05:49
shareable6 joined,
notable6 joined,
bloatable6 joined,
releasable6 joined,
unicodable6 joined,
evalable6 joined,
greppable6 joined
05:50
benchable6 joined,
squashable6 joined,
coverable6 joined,
quotable6 joined
05:51
tellable6 joined,
linkable6 joined,
reportable6 joined,
nativecallable6 joined,
bisectable6 joined,
statisfiable6 joined,
committable6 joined
06:00
reportable6 left
06:01
reportable6 joined
07:01
coverable6 left,
reportable6 left,
linkable6 left,
nativecallable6 left,
bloatable6 left,
tellable6 left,
releasable6 left,
committable6 left,
bisectable6 left,
unicodable6 left,
tellable6 joined
07:02
unicodable6 joined,
committable6 joined,
bloatable6 joined
07:03
releasable6 joined,
nativecallable6 joined
07:04
reportable6 joined,
coverable6 joined,
bisectable6 joined,
linkable6 joined
08:10
sena_kun left
09:52
linkable6 left,
evalable6 left
09:53
linkable6 joined
09:54
evalable6 joined
11:40
sena_kun joined
12:00
reportable6 left
12:01
reportable6 joined
12:28
squashable6 left
12:29
squashable6 joined
|
|||
| lizmat | sometimes I wonder if it would make sense to have a type of strand that would consist of elements with a join character | 12:30 | |
| Masterduke: or do we have something like that already? | |||
| tellable6 | lizmat, I'll pass your message to MasterDuke | ||
|
13:45
jgaz left
13:47
jgaz joined
15:45
evalable6 left,
linkable6 left
15:47
gfldex left,
evalable6 joined
15:48
linkable6 joined
18:00
reportable6 left,
reportable6 joined
18:18
gfldex joined
19:16
MasterDuke joined
|
|||
| MasterDuke | . | 19:16 | |
| tellable6 | 2023-06-11T12:30:45Z #moarvm <lizmat> Masterduke: or do we have something like that already? | ||
| MasterDuke | we have a bunch of heuristics in MVM_string_join about whether to create a new string of strands or a new flat string | 19:20 | |
| but we don't have a different string/strand type that's multiple elements and a single separator (unless there are just two parts to join of course) | 19:23 | ||
| completely random question. some of our ops have concreteness checks in interp.c, some have them in the implementing function, and some have them duplicated. is any one of those universally better than the others? | 19:38 | ||
| istr that putting them in the implementing function was a bit redundant when the op got jitted, since the jit would do it also | 19:39 | ||
| if that's correct, then moving them out of the implementing function and into interp.c would make sense. but i'm not at all confident about that actually being the case, and even if it is, how to know if/when that's true | 19:40 | ||
| nine | That's definitely true. Even better is that with syscalls the dispatcher and spesh can remove redundant checks as well | 20:23 | |
|
20:26
linkable6 left,
evalable6 left
20:27
evalable6 joined
20:29
linkable6 joined
20:30
sena_kun left
21:07
japhb left
21:08
japhb joined
21:13
japhb left
21:14
japhb joined
21:48
harrow left
22:03
harrow joined
|
|||
| jnthn | What nine++ said, the right direction is most ops moving towards being syscalls | 22:33 | |
| Since those have a very generalized framework for eliminating the repr/type checks | 22:34 | ||
| MasterDuke | hm. any suggestion as to which should be converted first? | 22:41 | |
| jnthn | Anything I/O related fits | 23:14 | |