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
..
assets
getting_started	Updated documentation:	2021-12-03 06:38:14 +03:00
guides	avoid memory allocation in base64decode	2022-01-24 07:24:34 +01:00
overrides	Changed Contributors section to a new style that includes GitHub contributors	2021-12-31 03:52:29 +03:00
stylesheets	Updated site:	2021-09-30 01:49:08 +03:00
index.md