|
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
reportable6 left
00:01
reportable6 joined
01:25
dogbert17 joined
01:29
dogbert11 left
03:26
notable6 left,
unicodable6 left,
coverable6 left,
statisfiable6 left,
greppable6 left,
benchable6 left,
sourceable6 left,
linkable6 left,
bloatable6 left,
evalable6 left,
committable6 left,
quotable6 left,
bisectable6 left,
tellable6 left,
releasable6 left,
nativecallable6 left,
squashable6 left,
shareable6 left,
reportable6 left
03:27
evalable6 joined,
tellable6 joined,
quotable6 joined,
sourceable6 joined,
benchable6 joined,
coverable6 joined
03:28
reportable6 joined,
committable6 joined,
linkable6 joined,
releasable6 joined,
statisfiable6 joined,
bloatable6 joined,
bisectable6 joined,
greppable6 joined,
nativecallable6 joined
03:29
notable6 joined,
shareable6 joined,
squashable6 joined,
unicodable6 joined
|
|||
| Woodi | right, not everything is struct :) | 04:27 | |
|
04:29
linkable6 left,
evalable6 left
|
|||
| Woodi | then memory areas for lexical scope would help to track usage. and when something is ascaping pack it into struct ? :) | 04:29 | |
|
04:31
linkable6 joined
04:32
evalable6 joined
|
|||
| Woodi | I think my problem with gc's is that looks that programs need to look for things that, somehow, are lost... then mark it and search in circles... my naive wishiness wants to have everything deterministic, black and white - used or not - from parse time... | 04:49 | |
|
05:32
evalable6 left,
linkable6 left
05:33
evalable6 joined
05:34
linkable6 joined
06:00
reportable6 left
06:01
reportable6 joined
07:12
linkable6 left,
tellable6 left,
notable6 left,
nativecallable6 left,
releasable6 left
07:14
linkable6 joined,
tellable6 joined,
notable6 joined
07:15
nativecallable6 joined,
releasable6 joined
09:36
mst left,
mst joined
10:03
squashable6 left
10:06
squashable6 joined
11:37
gfldex left
11:39
gfldex joined
12:00
reportable6 left,
reportable6 joined
13:12
dogbert11 joined
13:15
dogbert17 left
13:20
dogbert17 joined
13:22
dogbert11 left
14:05
MasterDuke joined
|
|||
| MasterDuke | timo: nice idea about doing a gc during blinking/saccades. not that applicable for most raku programs probably, but could help make using gc'ed languages more viable for user-interactive things | 14:08 | |
| and speaking of gc, there was some discussion at the RSC about making the unmanaged size of strings, arrays, etc pressure the nursery, like big integers do | 14:09 | ||
| oh, also done when allocating buffers for io it looks like | 14:13 | ||
| anybody have any thoughts about whether it should be done at all? and then if so, what heuristics to apply? | 14:14 | ||
| oh, s/RSC/RCS/ | |||
| lizmat | hehe :-) | 14:30 | |
|
16:12
linkable6 left,
evalable6 left
16:15
evalable6 joined,
linkable6 joined
16:31
dogbert17 left
18:00
reportable6 left
18:01
reportable6 joined
|
|||
| MasterDuke | huh, github.com/MoarVM/MoarVM/commit/bb7e757265 | 18:12 | |
| lizmat | maybe timo remembers | 18:13 | |
| MasterDuke | oh, this is almost exactly the same as something else that was discussed colabti.org/irclogger/irclogger_lo...07-19#l347 | 18:16 | |
| lots of heruistics to bikeshed in this area. multiple stands to reduce memory use? fewer strands to make iterating over a string faster? | 18:17 | ||
| lizmat | you mean irclogs.raku.org/moarvm/2017-07-19...22:40-0001 ? :-) | 18:18 | |
| MasterDuke | heh. different computers have different tabs already open... | 18:27 | |
| ugexe | so i think we just need to have a github.com/openjdk/jdk/blob/b94b67...#L377-L397 in MoarVM and to use it on any file paths for windows users to fix long paths. all the other backends already just support them afaict | 18:32 | |
| lizmat | would that imply that we could get rid of all the backslashy checks in Raku ? | 18:37 | |
| aka IO::Spec::Win32 ? | 18:38 | ||
|
19:35
linkable6 left,
evalable6 left,
linkable6 joined
19:38
evalable6 joined
20:07
vrurg left
20:35
vrurg joined
20:38
vrurg left
20:40
vrurg joined
20:54
brrt joined
|
|||
| ugexe | Unfortunately no. In fact we have to be extra sure we replace / with \. The reason \\?\ allows long paths on windows is because it bypasses the windows internal path normalization that uses MAX_PATH as one of its parameters. However, that normalization is what allows / in paths to work on typical windows paths. In other words: a \\?\ prefixed path won't work with / like it usually would | 21:01 | |
| brrt | \o | 22:01 | |
| link drop brrt-to-the-future.blogspot.com/20...m-jit.html | 22:33 | ||
|
23:03
brrt left
|
|||
| timo | brrt++ | 23:05 | |