japhb nwc10: Can you explain the reasoning behind c9d69dc658 ? My gut reaction would have been to go the opposite direction and fix the MoarVM ops so that they used the C library functions -- which might be using intrinsics or specially coded to maintain numerical stability or what have you. 03:48
linkable6 (2020-12-30) github.com/rakudo/rakudo/commit/c9d69dc658 Implement `sec`, `asec` and `sech` in terms of other NQP trigonometric funcs.
nwc10 japhb: there aren't C library intrinsics for any of those functions. MoarVM is just doing the same 06:36
same floating point arithmetic operations (plural), but from C
good *, #raku-dev
lizmat bisectable6: my @a = ["a", ["b", "c"]]; dd @a[1.0;0] 12:32
bisectable6 lizmat, Will bisect the whole range automagically because no endpoints were provided, hang tight
lizmat, Output on all releases: gist.github.com/df6d8d2a7ad3ed3c12...0bb40c34a9
lizmat, Bisecting by output (old=2018.06 new=2018.08) because on both starting points the exit code is 0
lizmat, bisect log: gist.github.com/c3a8d45c3e6e758d30...b181ee37c8 12:33
lizmat, (2018-07-09) github.com/rakudo/rakudo/commit/bd...6f154413dd
lizmat, Bisecting by output (old=2017.11 new=2017.12) because on both starting points the exit code is 0
lizmat, bisect log: gist.github.com/191431cd683f6094cb...de903562cb
lizmat, (2017-12-06) github.com/rakudo/rakudo/commit/00...3be857a615
lizmat, Output on all releases and bisected commits: gist.github.com/c897283ede38b89d41...6f56dc255a
sena_kun releasable6, status 18:29
releasable6 sena_kun, Next release in ≈10 days and ≈0 hours. 1 blocker. Changelog for this release was not started yet
sena_kun, Details: gist.github.com/c2d92682142180cc28...61d53f6d18
Geth ¦ problem-solving: melezhik assigned to rba Issue Independent CI server for Raku modules and infrastructure github.com/Raku/problem-solving/issues/258 23:07