Turbo-Base64 VS streamvbyte

** Cython bindings for Turbo Base64 [1] **

- 20-30x faster than the standard library

- Benchmarks faster than any other C base64 library

- Fastest implementation of AVX, AVX2, and AVX512 base64 encoding

- No other dependencies

[1] - https://github.com/powturbo/Turbo-Base64

Be direct and put the onus on the reporter/contributor to do more work before you will engage.

e.g., here is Daniel Lemire responding to a very open-ended bug report: https://github.com/lemire/streamvbyte/issues/72

There is something similar in customer service for my SaaS. Customers give horribly vague bug reports. I used to try to divine what they wanted. That way leads burnout. Instead, make them do more of the work.

You're right, I used a lot of unsafe. I started with the implementation from the C source and then my main goal was to add a bounds-check without sacrificing performance. I got there by manually unrolling the inner loop a few times and then bounds checking only once per iteration of the outer loop. So instead of 1 bounds check for every 4 inputs, I have one every 16 or 32 inputs (with a correspondingly more conservative bounds check).