Nick Logan

Indeed you can already know if there is a file listed in META6.json that doesn't exist by running `zef install .` since rakudo itself will raise an exception. However when...

> Clone it, cd to it, visually confirm the "resources" mismatch, and run Please re-read what I said and compare it to your repository: > Indeed you can already know...

While I don't think it makes sense for such a test to be run for anyone other than module authors, I've gone ahead and wrote a basic cut and paste-able...

You are referencing `IO::Handle` but all the code is `IO::Path`

> Marks a test as passed if the given code throws an exception. But your original code is not throwing an exception - a "bad proc" (by what I understand...

They are talking about `use fatal`, and I'm not sure if that would work here since process failures are not a traditional `Failure`

Note that the `/target-arm64` flag is not available with the version of dyncall we currently vendor. It was introduced in https://github.com/ugexe/dyncall/commit/c06b131325595add43568774bf0dddb04c9257e8#diff-b5e11e4ac62ecced8feac9095d90ae2a14627f91e8b5db85ac44547804f286e1R58

It is also possible that this detection is not needed and that the updated dyncall configure would Do The Right Thing using its own detection. When/if dyncall gets updated I'll...

I *think* that distribution is intended to be raku-RandomColor and not xxirakup6-RandomColor. [Its META6.json file](https://github.com/Xliff/raku-RandomColor/blob/9c1b5faf9b6a1ee93581cd00b2dcdda71d5a905f/META6.json#L15C5-L15C33) contains ``` "support": {"source": null}, ``` I'm kind of conflicted. I suppose it could be...

fwiw [here](https://gist.github.com/ugexe/7cf5d557ef40f21d2e35520d2a440423#file-base64-encoder-raku-L152-L171) is a custom encoder/decoder and a few tests exercising it