simdjson

simdjson copied to clipboard

Accept custom memory allocators (std::allocator)

16

This is related to https://github.com/simdjson/simdjson/issues/94 The idea is that we do very few memory allocations as it is, but we could, optionally, allow the user to provide us with a...

lemire

C++20 issue with comparison operators

13

Sorry about opening 2 tickets in a day, but I'm having some trouble started. With release 0.3.1, for `#include "simdjson.h"`, I get: ``` error LNK2019: unresolved external symbol "private: class...

h5rdly

fuzz simdjson for correctness

6

Current we fuzz simdjson for crashes and internal checks, but not for correctness. We have a framework for testing for correctness by generating random JSON and testing against different JSON...

lemire

Publish the API for simdjson with exceptions disabled

5

The API differs depending on whether exceptions are enabled or disabled. We currently publish and test mostly just the version with exceptions.

lemire

Add a difference_type for the array iterator

6

This makes it possible to do stuff like `std::distance(element.begin(), element.end())`

michaeleisel

E.g., https://www.sphinx-doc.org/

lemire

Have precise overhead-free error reporting (to the char)

3

Allow precise error reporting, so that we can narrow it down to the offending character when needed. cc @TkTech

lemire

Experiment with a "process by small blocks" strategy

11

We divide documents into small (e.g., 16kB) chunks. The document is parsed (in units of say 16kB) and possibly copied so it may be padded as needed. We run stage...

lemire

do away with padding

17

The padded string approach simplifies the code logic somewhat. However, it is not genuinely required. In time, it should be removed.

lemire

Investigate and increase fuzz coverage

3

Now when oss-fuzz provides pretty code coverage, it is easy to see which parts of the code are not fuzzed properly. Identify what can be done, and add fuzzers targeting...

pauldreik