|
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
00:10
reportable6 joined
|
|||
| nine | And up to 377 | 01:11 | |
|
02:19
notable6 left,
releasable6 left,
reportable6 left,
sourceable6 left,
bisectable6 left,
linkable6 left,
bloatable6 left,
nativecallable6 left,
coverable6 left,
committable6 left,
quotable6 left,
unicodable6 left,
evalable6 left,
greppable6 left,
benchable6 left,
statisfiable6 left,
shareable6 left
02:20
unicodable6 joined,
greppable6 joined,
quotable6 joined
02:21
bloatable6 joined,
bisectable6 joined,
sourceable6 joined,
reportable6 joined,
evalable6 joined,
benchable6 joined
02:22
committable6 joined,
notable6 joined,
statisfiable6 joined,
nativecallable6 joined,
releasable6 joined,
coverable6 joined,
linkable6 joined,
shareable6 joined
03:37
shareable6 left,
nativecallable6 left,
evalable6 left,
coverable6 left,
unicodable6 left,
reportable6 left,
notable6 left,
benchable6 left,
bisectable6 left,
statisfiable6 left
03:38
unicodable6 joined,
reportable6 joined
03:39
coverable6 joined,
evalable6 joined,
benchable6 joined,
nativecallable6 joined,
bisectable6 joined
03:40
notable6 joined,
statisfiable6 joined,
shareable6 joined
04:40
bloatable6 left,
committable6 left,
sourceable6 left,
releasable6 left,
reportable6 left,
bisectable6 left,
nativecallable6 left,
greppable6 left,
linkable6 left,
quotable6 left,
evalable6 left,
notable6 left,
shareable6 left,
unicodable6 left,
benchable6 left,
statisfiable6 left,
coverable6 left,
unicodable6 joined,
reportable6 joined
04:41
shareable6 joined,
evalable6 joined,
bisectable6 joined
04:42
releasable6 joined,
notable6 joined,
statisfiable6 joined,
quotable6 joined,
coverable6 joined,
bloatable6 joined,
benchable6 joined,
sourceable6 joined
04:43
committable6 joined,
linkable6 joined,
nativecallable6 joined,
greppable6 joined
05:11
frost joined
06:06
reportable6 left
06:09
reportable6 joined
10:17
sena_kun left
10:18
sena_kun joined
11:18
linkable6 left,
evalable6 left
11:20
linkable6 joined
11:21
evalable6 joined
|
|||
| nine | Looks like auto-generated protos are the next facet for the timing deliberations. | 11:48 | |
| Given just: multi sub foo() is export { }, this obviously needs to auto-generate a proto and this proto's meta object must be available to the export-trait, as this really means "export my proto". | 11:50 | ||
| lizmat | fwiw, I wouldn't be against removing auto-generate protos | ||
| they're really just too much magic imo | 11:51 | ||
| nine | That would break so much code out there. I mean, who is manually creating protos if they don't have to? So I don't see how that would be feasible. | 11:52 | |
| lizmat | I know... still, I can voice an opinion, no ? | 12:04 | |
| :-) | |||
|
12:06
reportable6 left
12:08
reportable6 joined
|
|||
| nine | You just did, so obviously you can :P | 12:15 | |
| jnthnwrthngtn | nine: Yup, there's multiple unresolved design questions in the area of multis in RakuAST, I'm afraid. | 12:21 | |
| nine | Actually, that comment is not totally off. There is the question of whether auto-generating protos is actually a task for the AST, or if it belongs in the parser. I.e. do people who create synthetic ASTs need to create those protos as well? | ||
| jnthnwrthngtn | AST. | 12:29 | |
| RakuAST is abstracted from some amount of syntactic detail, but not to that degree. | 12:30 | ||
| It's probably some kind of begin-time effect, much like package creation | 12:32 | ||
| Although it may be that we need to tease "begin time" apart a little bit | |||
| OK, two tiny fixes from me today in a spare moment. afk for a while :) | 13:06 | ||
|
13:08
linkable6 left,
evalable6 left
13:10
evalable6 joined
13:11
linkable6 joined
13:17
Geth left,
Geth joined
13:21
Geth left,
Geth joined,
sena_kun left
13:23
sena_kun joined
13:36
Geth left,
Geth joined
|
|||
| nine | jnthnwrthngtn: why are RakuAST::Parameter::Slurpy::Capture no RakuAST::Parameters? | 14:15 | |
| Ah, stupid question....because they just aren't. They're markers on the actual parameter objects | 14:16 | ||
| I'm really noticing that lack of sleep now. | 14:18 | ||
|
14:24
shareable6 left,
unicodable6 left
14:25
evalable6 left,
statisfiable6 left,
bisectable6 left,
statisfiable6 joined
14:26
shareable6 joined
14:27
unicodable6 joined,
evalable6 joined
14:28
bisectable6 joined
14:55
unicodable6 left,
shareable6 left,
evalable6 left,
evalable6 joined
14:56
releasable6 left,
vrurg left,
shareable6 joined,
vrurg joined,
releasable6 joined
14:57
unicodable6 joined
15:00
JoeyeS joined
15:05
linkable6 left
15:08
linkable6 joined
15:15
linkable6 left
15:17
linkable6 joined
15:25
frost left
15:28
JoeyeS left
15:29
JoeyeS joined,
JoeyeS is now known as Guest6423
15:32
Guest6423 is now known as JoeyeS
15:33
[Coke] left
15:36
[Coke] joined
15:38
linkable6 left
15:41
linkable6 joined
|
|||
| nine | Oh boy...how would I prevent a routine from getting added to the lexpad (i.e. a multi dispatchee)? | 16:00 | |
|
16:07
JoeyeS left
16:15
JoeyeS joined,
JoeyeS is now known as Guest1891
16:16
dogbert11 joined
16:18
dogbert12 joined
16:19
dogbert17 left
16:20
Guest1891 is now known as JoeyeS,
dogbert11 left
16:29
dogbert17 joined
16:30
dogbert12 left
16:36
dogbert11 joined
16:38
dogbert17 left
16:51
dogbert17 joined
16:52
dogbert11 left
17:17
dogbert17 left
17:25
dogbert17 joined,
JoeyeS left
17:28
dogbert11 joined
17:30
dogbert17 left
18:08
reportable6 left
18:09
reportable6 joined
18:46
dogbert17 joined
18:49
dogbert11 left
18:57
dogbert11 joined
18:59
JoeyeS joined
19:00
dogbert17 left
19:21
dogbert17 joined
19:23
dogbert11 left
19:32
dogbert11 joined
19:34
dogbert17 left
19:41
linkable6 left,
committable6 left,
greppable6 left,
bloatable6 left,
statisfiable6 left,
evalable6 left,
quotable6 left,
notable6 left,
benchable6 left,
sourceable6 left,
releasable6 left,
unicodable6 left,
coverable6 left,
shareable6 left,
reportable6 left,
nativecallable6 left,
bisectable6 left
19:46
greppable6 joined
19:47
unicodable6 joined,
sourceable6 joined,
releasable6 joined,
shareable6 joined,
evalable6 joined
19:48
quotable6 joined,
reportable6 joined,
statisfiable6 joined,
notable6 joined,
bloatable6 joined,
benchable6 joined
19:49
coverable6 joined,
nativecallable6 joined,
linkable6 joined,
bisectable6 joined,
committable6 joined
|
|||
| MasterDuke | huh, look like github.com/MoarVM/MoarVM/commit/e7...44daa39e52 is already supposed to detect a working stdatomic.h | 20:03 | |
| ah, but that only uses the probe to check for whether we can use mimalloc | 20:05 | ||
| Geth | MoarVM: MasterDuke17++ created pull request #1699: Take stdatomic.h probe into account in decision whether or not to use c11 atomics |
20:25 | |
|
20:59
JoeyeS left
21:54
dogbert11 left
21:56
dogbert11 joined
|
|||
| Geth | MoarVM: d7dee3a282 | (Daniel Green)++ | Configure.pl Use stdatomic probe in using c11 atomics decision Had to move the probe earlier, and then also copy the minimal ldlib setup code. |
21:57 | |
| MoarVM: 794e1d589b | MasterDuke17++ (committed using GitHub Web editor) | Configure.pl Merge pull request #1699 from MasterDuke17/use_stdatomic_probe_to_decide_whether_to_use_c11_atomics |
|||
|
22:33
JoeyeS joined
22:43
JoeyeS left
22:56
JoeyeS joined
23:01
JoeyeS left
23:48
JoeyeS joined
|
|||