Why yet another json package in Rust ?

This crate makes several trade-offs that are tuned for bigdata and document database.

• Support for 128-bit signed integers.
• Deferred conversion for JSON numbers.
• Serialization from Rust native type to JSON text.
• De-serialization from JSON text to Rust native type.
• CRUD operation on JSON documents, using JSON Pointer.
• Sorted keys in property object.
• Streaming JSON parser.
• Support JSON5 standard.
• Common arithmetic and logic operations.
• Sortable JSON.

API Documentation

Deferred conversion for numbers

Converting JSON numbers to Rust native type is not always desired. Especially in the context of bigdata where data is stored in JSON format and we need to lookup, only, specific fields within the document.

This implementation provides deferred conversion for JSON numbers that leads to a performance improvement of upto 30%.

CRUD operations on JSON documents

Using Json Pointer it is possible to identify a specific field nested within a JSON document. For Example, with below document:

  {
    "age": 26,
    "eyeColor": "green",
    "name": "Leon Robertson",
    "gender": "male",
    "company": "AEORA",
    "phone": "+1 (835) 447-2960",
    "tags": [ "officia", "reprehenderit", "magna" ],
    "friends": [
      {
        "id": 0,
        "name": "Glenda Chan"
      }
    ]
  }

• /age shall point to value 26.
• /friends shall point to value [{"id": 0, "name": "Glenda Chan"}],

List of operations

• Get a field nested within a JSON document using JSON Pointer.
• Set a field nested within a JSON document.
• Delete a field nested within a JSON document.
• Append string or array field withing a JSON document.

JSON5

• Object keys may be an ECMAScript 5.1 IdentifierName.
• Objects may have a single trailing comma.
• Arrays may have a single trailing comma.
• Strings may be single quoted.
• Strings may span multiple lines by escaping new line characters.
• Strings may include character escapes.
• Numbers may be hexadecimal.
• Numbers may have a leading or trailing decimal point.
• Numbers may be IEEE 754 positive infinity, negative infinity, and NaN.
• Numbers may begin with an explicit plus sign.
• Single and multi-line comments are allowed.
• Additional white space characters are allowed.

Track this activity

Help wanted

• Add readme badges #1.
• Alternate string parsing for non-unicode JSON #3.
• JSON5 implementation #4.