Florian Bernd

Hi there, thanks for submitting your patch 🙂 We will try to integrate this upstream. Pasting the patch here for reference: ```diff --- a/include/Zycore/Defines.h +++ b/include/Zycore/Defines.h @@ -131,6 +131,8 @@...

@athre0z We should probably as well introduce a generic `ZYAN_ARCH64` (open for better name suggestions). Same for 32-bit environments.

https://github.com/dorny/test-reporter#github-limitations > Check Runs are created for specific commit SHA. It's not possible to specify under which workflow test report should belong if more workflows are running for the same...

Is it even a failure if no test results have been found? It should rather be a warning in my opinion. This behavior already caused issues for me in the...

> For example, if no test results are found, because perhaps the file name was misspelled or so, i think it is good if the action marks itself as failed....

The build command was `python ../mfile.py examples` in this case. Executed from within a `Build64` directory inside the `xed` folder. The following is an example of what Visual Studio uses...

@marjevan Yes, after pulling the latest `mbuild` and `xed` heads, the build still outputs: ``` [MBUILD WARNING] Command execution failed. Waiting for remaining jobs and exiting. R: 0 P: 114...

@samuelchmiel Hi there, I'm the new maintainer of the library, but NEST currently has low priority for me as well. I'm happy to accept PRs, but besides from that, it...

No hurries 🙂 I just noticed that while comparing XED decoder output to Zydis decoder output and wanted to let you know!

@AArnott Thanks for the reply. > The @ prefix isn't part of the parameter name. That's just C# syntax. At runtime, where MessagePack is reflecting over your members, there is...