Elizabeth Mattijsen
Elizabeth Mattijsen
Further golfed to: $ raku -e 'use nqp; nqp::splice(my int @a,array[int].new(:shape),0,1)' Segmentation fault: 11 so it looks like a problem with nqp::splice()
If this works out, then maybe all **29** ops that have a string index, should get this treatment: ``` $ bceval c '.map({.name if .operands.first("str")}).unique.elems' 29 ``` Which in the...
Heh, quite a can of worms :-) So, all printf / fmt related stuff in 6.e will be based on `Formatter` class. However I'm still not sure whether that should...
No idea. How huge is the JSON file? Could you provide the output with `--dont-catch` ?
Ok, looks like a memory corruption in MoarVM :-(. Multi-threading is hard! Does it also crash with `--degree` ? OOC, which version of Rakudo are you using?
Hmmm `--matches` appears to be a non-existent argument? Do you have a shortcut for it? Also: you don't appear to be using any JSON specific functionality. So I tried to...
Hmm.. then I would suggest you upgrade to 2024.07 anyway: there's been some other work on MoarVM as well, and maybe, just maybe it got fixed.
> There is something wrong with multithreading Interesting. The `count-only` feature uses the :mapper: feature of the "rak" module, and that's supposed to be thread-safe...
> There must be a link with paraseq ! Indeed. But `ParaSeq` just uses Raku's features, albeit in a more optimal way than the standard `.hyper` functionality. So maybe it's...
> rak -i abc --count-only --matches-only xab OOC, why the `--matches-only` ? Especially if you have a fixed string?