Pavel P

### Description / Steps to reproduce the issue I'm on win11 pro. Usually, I have like 5-10 msys2 console windows open (for multiple c++ environments). I run sometimes tests in...

Check STATIC_BMI2 instead of __BMI2__

8

`ZSTD_ENABLE_ASM_X86_64_BMI2` already implies BMI2 by its name, and by the way it tests defines

I have a warning that I get when compiling code that uses boost::beast. This happens only on msys2 when compiling with g++ (my version is 15.1.0). This warning doesn't really...

For testing reasons, I build my app also using cygwin. Pretty much everything worked out of the box except something that I wouldn't expect to fail: boost-asio. The problem is:...

recieved -> received errror -> error whehter -> whether queueing -> queuing (both are ok) behaviour -> behavior (use US spelling)

wslay supports sending `close` frame using `wslay_event_queue_close` or `wslay_event_queue_msg` functions. However, it looks like using wslay_event_queue_msg with non-empty message triggers a bug where the generated frame isn't handled on the...

Would it be a good idea to reuse memory buffers instead of making allocations on each incoming/outgoing websocket message?

avx version is not correct

1

You should comment it out, so that ppl don't end up using it blindly sample string that fails: ```c++ char str[3] = {0xce, 0x81, 0x49}; ``` rfc version produces `"5d74f9b877a366a09d8af319d22c45c2"`,...