Problem:

When you initialize a stuffer with an existing blob, the typical pattern is to write

struct s2n_blob blob;
struct s2n_stuffer stuffer;

GUARD(s2n_stuffer_init(&stuffer, &blob));
GUARD(s2n_stuffer_write(&stuffer, &blob));

This causes a memcpy to write to overlapping pages, which is undefined behavior. A workaround is to use s2n_stuffer_raw_write, but this st

The documentation should always be in sync with the latest changes. Currently, this involves me manually building it and pushing it into an S3 bucket. That could happen automatically through CI.

Additionally, it would be great if we could display a drop-down in the doc that allows viewing documentation for older versions of Zydis as well, similar to what docs.rs does for Rust

Describe the problem you are trying to solve.
Adopting Flecs would be made easier if prebuilt binaries were available for the CI platforms.

Describe the solution you'd like
A configuration that makes binaries available for a CI that supports it.

Don't mean to be that guy, but in the Comparison section at the end of the starting paragraph, it says marcos when it should say macros.

[update]
I am requesting a list of status_code and their meanings returned by the following function reportedStateCallback(). My port is esp-azure but this status_code should be generic. Thanks.

[original]
I'm using the esp-azure port but the c port has the same function, a callback function when device completes sending device twin update:

static void reportedStateCallback(int status

The vp instructions does not decode well.
For example:
"c5 f1 ef c9" should be decoded to "vpxor xmm1,xmm1,xmm1" (instead of "lds...").
"c5 f5 74 01" should be decoded to "vpcmpeqb ymm0,ymm1,ymmword ptr [ecx]" (instead of "lds...").

The website seems to reflect API changes in 0.6 but no tag exists. Is 0.6 still in progress or is the release tag missing?

cbor_item_t *cbor_tag_item(const cbor_item_t *item)
Get the tagged item.
Return
incref the tagged item
Parameters
item[borrow]: A tag

This API does not increment the reference count so either the documentation is incorrect or the code is. The result of this is a system crash, primarily due to the change that checks the reference count:
https://github.com/

pDescription may be null and causes a hard-fault when observers are notified of a resource update.
https://github.com/Lobaro/lobaro-coap/blob/b6b5ced0f7d013022c848d5f3da4ddb757339b6c/src/coap_interaction.c#L279

It's set to NULL when an null or empty string is passed in as a resource description on CoAP_CreateResource:
https://github.com/Lobaro/lobaro-coap/blob/d7a4c79ad2217f744ac9757d2b4b

Reference implementation in milagro-c
apache/incubator-milagro-crypto-c#47

For readability and maintenance the new BLS implementation can be made in Lua script with a very small computational overhead in Zenroom.
Implementaiton: src/bls192.c.in
Example usage: examples/example_bls_sss_ZZZ.c.in

In src/hsluv.h the documentation says for rgb2hpluv: @param[out] ps Saturation. Between 0.0 and 100.0. but I think this is incorrect.

When passing the RGB values 1,1,0 (yellow) the returned Saturation is 1784.236 and for other colors it is also bigger then 100. The values are not wrong according to the CIELUV color space, only the documentation states it incorrectly.

The result from `