Let std::string and char * casters also accept bytes
#23
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
std::string and char * casters also accept bytesstd::string and char * casters also accept bytes
17 tasks
|
Humm, I don't think I like this one -- probably more in the territory of a custom type caster that you could define in your project. |
b6837e0 to
13dbff1
Compare
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.
I don't quite know whether I like this. Ideally, we'd be able to tell from C++ whether something is intended to be UTF-8 or not. (Maybe an argument attribute? An entirely separate type?) Examples where this is relevant include Unix filenames (bytes, not really UTF-8). I encountered it for passing compiler options to OpenCL's
clBuildProgram, where any implicit encoding change is a risk.Still to do: