Paulo Cabral Sanz

@omni-viral Shouldn't the assert also be there in release? Since in release it will wrap and a bunch of unexpected things will happen?

You have to create your own handler, it's not hard. You just have to reimplement two places, the boilerplate can get annoying tho. Implement your custom handler class, like this...

It seems most bugs 3.0 went through before release were related to mem-leaks, which are not memory errors and can be triggered with safe code. Buuut it seems like a...

In the last month a few of our clients started experiencing the official whatsapp mobile app crashing repeatedly when the QR code provided by this library is scanned. We have...

Honestly I don't know, I inherited a lot of go code that derives from this library. We actually fixed a bug in images attachment download, but I think it's mostly...

It seems #569 is about the same problem, we stopped experiencing it for now, but it seems it still happens sometimes.

We stopped experiencing any problems. I'm ok with closing it and if it happens again we refile it.

espressif/llvm-project#4 implies that all of the repo's changes have been merged to upstream LLVM, although the PR hasn't been closed yet. What are the next steps?

I think the first step is opening those issues on the upstream rust repository, and we should then track them with a reference issue (maybe here because that's the repository...

I don't have a windows system either, the benchmark wasn't done by me, but another user got similar results in linux, maybe there is a common denominator. https://www.reddit.com/r/rust/comments/ejx7y8/blog_post_mutexes_are_faster_than_spinlocks/fd3taac/ Linux system...