Details
-
Bug
-
Resolution: Fixed
-
Major
-
1.0.0-beta
-
None
-
None
-
1
-
SDK26: KV,ES8, Known Issues
Description
The client currently uses std::string almost exclusively to represent both strings of utf8 characters, as well as strings of arbitrary bytes. This leads to issues when performing automatic translation in various SDKs (this came up in Node.js with v8), since in many languages there is a differentiation in semantics between a string and a buffer.
Attachments
Issue Links
- blocks
-
JSCBC-1054 Avoid unnecessary byte conversion due to std::string incompatibility with v8::String
- Resolved