Martchus
/
reflective-rapidjson
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fix plural of pointer in README.md

This commit is contained in:
Martchus 2022-02-05 22:28:20 +01:00
parent 59ff3c19eb
commit 22611457f9
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -68,12 +68,12 @@ The following table shows the mapping of supported C++ types to supported JSON t
| `JsonSerializable` | object | | `JsonSerializable` | object |
### Remarks ### Remarks
* Raw pointer are not supported. This prevents * Raw pointers are not supported. This prevents
forgetting to free memory which would have to be allocated when deserializing. forgetting to free memory which would have to be allocated when deserializing.
* For the same reason `const char *` and `std::string_view` are only supported for serialization. * For the same reason `const char *` and `std::string_view` are only supported for serialization.
* Enums are (de)serialized as their underlying integer value. When deserializing, it is currently *not* checked * Enums are (de)serialized as their underlying integer value. When deserializing, it is currently *not* checked
whether the present integer value is a valid enumeration item. whether the present integer value is a valid enumeration item.
* The JSON type for smart pointer depends on the type the pointer refers to. It can also be `null`. * The JSON type for smart pointers depends on the type the pointer refers to. It can also be `null`.
* If multiple `std::shared_ptr` instances point to the same object this object is serialized multiple times. * If multiple `std::shared_ptr` instances point to the same object this object is serialized multiple times.
When deserializing those identical objects, it is currently not possible to share the memory (again). So each When deserializing those identical objects, it is currently not possible to share the memory (again). So each
`std::shared_ptr` will point to its own copy. Note that this limitation is *not* present when using binary `std::shared_ptr` will point to its own copy. Note that this limitation is *not* present when using binary