Introducing libcpp_utf8_output_string type #71
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
to python (unicode) strings on function return
Closed
narekgharibyan
added a commit
to narekgharibyan/keyvi-1
that referenced
this pull request
May 23, 2018
(OpenMS/autowrap#71) - set minimum required autowrap version
narekgharibyan
added a commit
to KeyviDev/keyvi
that referenced
this pull request
May 23, 2018
(OpenMS/autowrap#71) - set minimum required autowrap version
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces
libcpp_utf8_output_stringtype, which decodes bytes to strings/unicodes on function return.This was initially implemented for https://github.com/KeyviDev/keyvi project as currently both
libcpp_stringandlibcpp_utf8_stringtypes are converted tobyteson function return.