01:02 kjp left 01:03 kjp joined 01:04 kjp left 01:05 kjp joined 01:35 CultOfTheGlenda joined 04:07 CultOfTheGlenda left
ab5tract Anyone still running 16.04 can use an older build of rakudo 06:27
I don't think there is any reason whatsoever to cater to a (likely imaginary) corner of the user base who for some reason needs to run an completely exploitable version of an operating system 06:28
I feel the same about 32-bit ISAs, fwiw 06:35
But at least supporting that doesn't involve using a decade old version of Ubuntu to build things
what about the codegen from gcc? Are we sure that we aren't missing out on improvements to the compiler that were introduced in the last 10 years? 06:36
Geth nqp/main: 71757cefad | (Elizabeth Mattijsen)++ | tools/templates/MOAR_REVISION
Bump MoarVM to get uint JIT fix, MasterDuke++
08:59
rakudo/main: 4307ec0149 | (Elizabeth Mattijsen)++ | tools/templates/NQP_REVISION
Bump NQP to get uint JIT fix, MasterDuke++
09:10
roast: b822369da2 | (Elizabeth Mattijsen)++ | S02-types/signed-unsigned-native.t
Add test for #5954
09:26
rakudo/main: 7192f67afb | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | lib/Test.rakumod
Add exit-ok to Test module

As promised in github.com/Raku/problem-solving/is...3263735792 the "exit-ok" subroutine takes a Callable (which is expected to call exit() ), an integer value (0 by default), and an optional description.
If the code performs an "exit", then the value will be checked: it will be judged ok if the value matches, else it will be a nok.
If the code does not execute an "exit", then it will also be a nok.
09:29
10:24 lizmat left, guifa_ joined, lizmat joined, guifa left, leont left, zostay left, leont joined, zostay joined