Commit Graph

4 Commits

Author SHA1 Message Date
Thomas Neumann
15085a9f95 avoid memory allocation in base64decode
Every single call to base64decode allocates a mapping table for all
base64 characters. This is quite wasteful, as the map is in fact static.
We could use a static variable here, but that would have unpleasant consequences
if we ever encounter input with non-valid base64 characters (which
implicitly modifies the map).

The number of character ranges for base64 is quite low (3, plus 4 exceptions),
thus we can simply check that explicitly in code instead of using a dynamic hash table.
2022-01-24 07:24:34 +01:00
Mr-Destructive
943bc82819 Fixed typos in docs/guides 2021-12-08 10:39:55 +05:30
Farook Al-Sammarraie
b64fc0e34c
typo fix
Co-authored-by: Luca Schlecker <luca.schlecker@hotmail.com>
2021-12-04 04:16:50 +03:00
The-EDev
b309bda160
Updated documentation:
added auth guide
updated macos setup
2021-12-03 06:38:14 +03:00