jasder
/
simdjson
1
0
Fork 0
Code Issues Pull Requests Releases 2 Wiki Activity

Being more specific regarding the padding. (#1228) 

* Being more specific regarding the padding.

* Even more precise.
This commit is contained in:
Daniel Lemire 2020-10-14 13:35:51 -04:00 committed by GitHub
parent c85b6682e0
commit 001be23258
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/basics.md
View File

@ -108,7 +108,7 @@ SIMDJSON_PADDING bytes at the end) and calling `parse()`:
```c++ ```c++
dom::parser parser; dom::parser parser;
dom::element doc = parser.parse("[1,2,3]"_padded); // parse a string dom::element doc = parser.parse("[1,2,3]"_padded); // parse a string, the _padded suffix creates a simdjson::padded_string instance
``` ```
The parsed document resulting from the `parser.load` and `parser.parse` calls depends on the `parser` instance. Thus the `parser` instance must remain in scope. Furthermore, you must have at most one parsed document in play per `parser` instance. The parsed document resulting from the `parser.load` and `parser.parse` calls depends on the `parser` instance. Thus the `parser` instance must remain in scope. Furthermore, you must have at most one parsed document in play per `parser` instance.

2
doc/basics_doxygen.md
View File

@ -89,7 +89,7 @@ SIMDJSON_PADDING bytes at the end) and calling `parse()`:
``` ```
dom::parser parser; dom::parser parser;
dom::element doc = parser.parse("[1,2,3]"_padded); // parse a string dom::element doc = parser.parse("[1,2,3]"_padded); // parse a string, the _padded suffix creates a simdjson::padded_string instance
``` ```
The parsed document resulting from the `parser.load` and `parser.parse` calls depends on the `parser` instance. Thus the `parser` instance must remain in scope. Furthermore, you must have at most one parsed document in play per `parser` instance. The parsed document resulting from the `parser.load` and `parser.parse` calls depends on the `parser` instance. Thus the `parser` instance must remain in scope. Furthermore, you must have at most one parsed document in play per `parser` instance.