MasterDuke17

Or a more fleshed out https://github.com/rakudo/rakudo/tree/master/t?

I would suggest the vertical "Author" problem should be fixed before there's a redirect.

> I could make the header dual c/c++ probably If you're willing to do that MoarVM could probably just submodule the repo and use the header directly instead of relying...

@samcv ping. AIUM (As I understand myself) in https://github.com/MoarVM/MoarVM/pull/1498#discussion_r641624709 I'm not sure the proposed fix was correct. Are you able to take a look at this again?

> @MasterDuke17 please ping me again in 7 days if I haven't replied to this message yet. Sorry for the delay in answering the question. Will try to get to...

The changes in src/strings/decode_stream.h don't seem to be necessary anymore. At HEAD of master, neither gcc 10.3.0 nor clang 12.0.0 show a warning there. There aren't any warnings in src/strings/shiftjs.c...

I looked at the Makefile I have currently in MoarVM and if I'me reading it correctly, we don't use the build scripts, and instead just list the particular libuv source...

There are also 9 fails in t/spec/S03-operators/bit.t ``` not ok 19 - long string bitwise ~&, truncates # Failed test 'long string bitwise ~&, truncates' # at t/spec/S03-operators/bit.t line 58...

Upon a reread of “This operator is distinguished from numeric bitwise AND in order to provide bit vectors that extend on the right rather than the left (and always do...

After switching to padding on the right, in addition to the single fail in t/nqp/059-nqpop.t, there are three fails in t/spec/S03-operators/bit.t: ``` not ok 19 - long string bitwise ~&,...