| Geth | MoarVM: MasterDuke17++ created pull request #1872: Difference fast path when comparing 8-bit strings |
02:19 | |
| MoarVM/main: aff9c1c9af | (Daniel Green)++ | src/strings/ops.c Difference fast path when comparing 8-bit strings If we're comparing 8-bit strings and there's a difference, but no synthetics involved, we don't need to go through the generic grapheme iterator path. |
03:54 | ||
| MoarVM/main: 81aefe5412 | MasterDuke17++ (committed using GitHub Web editor) | src/strings/ops.c Merge pull request #1872 from MasterDuke17/fast_path_when_difference_for_8-bit_strings |
|||
|
04:13
bartolin left
04:24
bartolin joined
09:19
japhb left
09:26
japhb joined
|
|||
| lizmat | Bunped NQP and Rakudo, not seeing any speed increase, in fact the first impression is a slow down :-( | 09:34 | |
| not much, will keep monitoring | |||
| hmmm could have been a time machine backup running at the same time :-) | 09:36 | ||
|
09:37
sena_kun joined
10:07
sena_kun left
14:20
vrurg joined
18:53
sena_kun joined
|
|||
| timo | hm. do we just never get line numbers in backtraces when we are in a jitted frame? | 20:51 | |
| and i think we're not looking at inlines of the current frame when we're outputting stack traces either | 20:54 | ||
| Geth | MoarVM/main: fd9da869dc | (Justin DeVuyst)++ | docs/release_guide.md Update release guide to align with current practice. |
21:20 | |
|
23:02
sena_kun left
|
|||